DPI Wizard

If you enter the same monitor size for input and output game it doesn't matter, it is not used for the sensitivity calculation.
If you enter a different size the calculator will do a conversion, and the correct size to use is the actual diagonal size for most accurate results.

For most 3D games nothing changes when you change resolution but keep the same aspect ratio. The FOV and 360 distance will be the same. There are a couple of games that are directly affected by resolution, but that's not normal.
For Windows however you probably want to change DPI if the old one feels too slow. And if you want to play with this new DPI you also need to re-calculate the sensitivity for your games. 
The calculator will scale the sensitivity according to the monitor size if you input two different ones. Some prefer this when changing monitor size, but this is purely based on size and not resolution. This does not work for 360 distance obviously as it stays the same, which is why you only get a difference for the ADS in your example. To also scale hipfire you need to change it to MDV 133% as well. This will change the calculated hipfire sensitivity, and all ADS will be the same as before since they scale to the now changed hipfire.

Since the Legacy option in Warzone is based on a 4:3 FOV of 65 you have to trick the calculator a bit. 
As you have already matched the hipfire FOV you can set the hipfire conversion to 360 distance and change the FOV for Warzone to Hdeg 4:3 65 and set ADS and Scope to MDV 0%.
This will result in the output for Warzone showing 1.0 for all scopes as it should. I've set the zoom all for BF2042 to 200 here instead of all scopes, so they can be left at 100:
https://www.mouse-sensitivity.com/?share=98ec2cbf7dac1c958bd21b87d8076607

Correct, only 360 distance is available in the free version but that isn't an option for 2D conversions (obviously).

Can you please provide your exact conversion by using the purple share button?

Nice, thanks for letting me know. Updated it now!

Since you have the monitor distance coefficient set to 1.33 you should set the ADS and scope to 133% like this:
https://www.mouse-sensitivity.com/?share=c308d0ee5799e2cfb0079619453145e2
The only question is if you would like the hipfire at FOV 120 to match the 360 distance to 100 (like the link above) or follow the same MDV 133% scaling like this scopes:
https://www.mouse-sensitivity.com/?share=c0136fbed6fbcb23614637c6f62444b7

This is correct for getting 40 cm for hipfire and all aims matched to MDH 100% (i.e. the same distance moving to the edge of the monitor). The aim scaling in Hunt is all over the place which is why you get such different numbers for all the aims.

Ok, for BF 2042 the calculations will be off, how much depends on your settings. This is because the beta has issues with acceleration and terrible mouse input registration. Hopefully this will be fixed for the release.

See this thread

Energy Assault is already supported, so you can do the calculation like this: https://www.mouse-sensitivity.com/?share=7eed59a118e957d05a9a68d58d622f15
Technically this calculates the Roblox main sensitivity, but the numbers are interchangeable so you should set the Energy Assault sensitivity to the calculated value.

Added 👍

Then this would be correct: https://www.mouse-sensitivity.com/?share=cb37432641898b8f1790fa50e40fc75a
MDH 75% is only correct for 16:9, so when you stretch you need to use MDV 133.3333% instead to keep it consistent.

Most of the time in Roblox the FOV does not change when going first person vs. third person, but there can obviously be exceptions. 

If you want to scale the sensitivity to monitor size, simply enter a different monitor size for the output:
https://www.mouse-sensitivity.com/?share=f76db10c429b0ba7d128576e51b8ae3a

This is 100% sure an issue with the game. As stated in the notes, if you experience any difference in later versions, try the same fixes. Minecraft has never changed the actual sensitivity, but have had issues with FPS, vsync, polling rates and conflicts with keyboard input and sensitivity, which this is likely related to also. If you can try a tool like this in both versions you should see that they are exactly the same (granted vsync is off, and expect a few tests to be slightly off due to packet registration issues in the game), any difference you experience is basically down to a bug in the game that is inconsistent and impossible to account for.
Also, the difference between the old pre and post 1.13 calculations was just a slightly lower base sensitivity (about 1.3 % lower) that was so insignificant that it was barely measurable. It turned out to be down to packet losses in the old versions, which again doesn't actually change the sensitivity so having it as a separate calculation was wrong. The base is the same, and how the bug is experienced will vary a lot.

The FOV type will automatically change to the type the game you select uses. This means that the value of i.e. 60 will result in a different actual FOV for games that use vertical degrees compared to ones that use horizontal degrees.
The FOV type itself does not affect the sensitivity, but if you want the same actual FOV in different games you need to pay attention to this. 

If you mean by all ADS sens default that all ADS in Apex is 1, then this is the correct way to do it: https://www.mouse-sensitivity.com/?share=c6add5549a3c5cc5a8a1bb725a614e94

Have you changed the MouseSensitivityMultiplierUnit value in the config file? In-game calculation assumes it is set to the default of 0.02.

It might be that changing monitor size in combination with stretched resolution has a bug I see, as it assumes you have a 24" 4:3 monitor and are converting to a 24.5" 16:9.
0.55 is correct, if you do like this example to change the horizontal FOV to 90 while keeping your 360 distance you'll get 0.55: 
https://www.mouse-sensitivity.com/?share=1a41515e93266b224305e65fee159963
I'll fix this in the next update!

If you just change the settings in MW and not the conversion setup, nothing changes in the calculation for the output game, you are just changing how sensitivity is calculated for MW.
If you change MW to relative and 1.33 you also need to set the conversion for ADS and Scope for MDV 133%:
https://www.mouse-sensitivity.com/?share=50cfa04fdfb857a843abddff9f05aa9f

Added now

And this is correct, the coefficient has no effect on hipfire sensitivity (Sensitivity 1), only aims.

They are only the same at 70: https://www.mouse-sensitivity.com/?share=280ec8fb3d437253292beae4fd2b00c2
Apex uses a multiplier visible in the config file to the 70 value (so the max in-game of 110 equals 1.55 in the config file which equals 70*1.55=108.5). There's a small offset from the in-game value, probably down to lazy coding by the devs.

Focus is classified as an ADS, so you need to set your ADS setup to 360 distance if you want to have it the same as hipfire.