Groen28

Yes, use the same value.

Correct

Using the "All" aim and adjusting the conversion setup so the calculated zoom sensitivity for the game you are converting from corresponds to your settings is the recommended way.
One thing though, Battlefront 2 has a big issues with acceleration and mouse smoothing so it's generally a bad game to use as the source for your conversions.

Correct, since it's based on Frostbite 3 I was able to deduce the hipfire and aim sensitivity since it's related to (but not the same as) Battlefield games. Vehicles are generally a lot trickier since they usually have a built in negative acceleration or max turn speed etc, so with the added smoothing and acceleration already present it makes it really hard to analyze.

The GstInput.MouseSensitivity you get from your config file, where it defaults to 40. You can in theory use any value between 1 and 100 here, but 100 is recommended as it fixes a critical issue with dropped packets from the mouse. 
You get a different 360 distance in your screenshots because you use a different GstInput.MouseAimSensitivity (1.510511 vs 0.7).
Correct, this is also shown in-game if you hover over the sensitivity options.

Any update on Anthem FOV option?  Like the above poster said FOV support is available now.