DPI Wizard

In that case you can just use the normal Black Ops III calculations, they are the same as the boii client but with the fovscale locked to 1.

Nothing is really necessary as it depends on you preference. The positive of matching everything to Windows using MDV 0% is that 1 pixel movement will always be the same. The downside is that this will drastically affect especially hipfire when your FOV is different. 360 distance is usually preferred for hipfire as it keeps a constant movement for orientation rather than aim. So you know how far to move your mouse to turn around a corner etc. With MDV 0% or a match made to Windows/Desktop, this distance will change depending on your FOV. And while it keeps the aim consistent, this is usually less important than navigation when it comes to hipfire.
But it all depends on the game and your preference, nothing is right or wrong, what is important is what feels natural to you.

It's unsupported because the sensitivity is directly affected by the framerate, making it very unstable and any sensible calculation impossible.
So as to your question of "when", it will be added when the devs fix this issue

Sensitivity 2 is the Coefficient (you can see this in the output), and the 0.68 is the scale for the ADS conversion, where also enter the coefficient so it matches, like this:
https://www.mouse-sensitivity.com/?share=f42f0a7af910c8457de15d13bdc1db5a

Trigonometry
https://www.wolframalpha.com/input?i=tan((PI*74)%2F360)*cot((PI*66.6)%2F360)

The relation between the actual FOV and the monitor distance is calculated, in this old video you can see it visualized:
 
This is Monitor Distance 100%, and depending in whether you use the horizontal or vertical FOV to do this, you get either MDH 100% or MDV 100%. The method will for many make the scopes feel too fast, since you need to match the movement to the edge of the monitor (side for MDH, top for MDV) to actually match the movement. Monitor Distance 0% however, will match the tracking speed, i.e. the rate at which you move your mouse to track a moving target.

Actually, do you have zoom enabled in Windows? 150%? It might affect certain games like Roblox. If this is the case, multiply the sensitivity by 1.5 to compensate for the zoom.

Just set the FOV to Vertical (1:1) and use the same value (86).

You can try to use the same conversion for hipfire as your ADS and scopes: https://www.mouse-sensitivity.com/?share=6d0061b61632e557e421e98084031850

Set the ADS and scope scale to 99.083: https://www.mouse-sensitivity.com/?share=17de5bb30efe2973a47d30d9f48c41bf

x and y are still different, but they have halved the x sensitivity so they are much closer. I've updated it now

What you said is correct, and it has to be this way to make any sense. If the scopes were matched to the hipfire of the output game you would not get any consistency unless you also match the hipfire FOV between the games.
Consider this example converting from Overwatch with FOV 103 to Overwatch with FOV 80: https://www.mouse-sensitivity.com/?share=43c8dace9347072001b6b2962b254eaf
The FOV change only affects hipfire, the zoom FOV stays the same. So the sensitivity (360 distance) for the zoom should also stay the same to keep it consistent. If they were matched based on FOV 80 instead, you would get a completely different sensitivity for identical zoom levels.
Click the reverse calculation button between the input and output game

The "Zoom Level: Iron Sight" is also 1.25x, at least on the weapons I've tried so far. Just switch between 1.25x and iron sights and you'll see it's the same.
There might be a 1.00x somewhere, but it's really hard to find!

Good idea, I've added it to the "Actual VFOV" line in the advanced output now!

Also note that aspect ratio usually does not change the 360 distance (with some exceptions), so converting between different aspect ratios will in most cases result in the same sensitivity when using 360 distance.

Yes, you need to match the conversion setup to your game settings. For CSGO this means setting ADS and Scope to MDV 133.3333% and Scale 100%. This will calculate the zoom sensitivity to "1" for all scopes. When converting to any other game, the same conversion will be applied, preserving the exact same sensitivity based on the FOV of the scopes.

For hipfire you can either to the same, or keep it at 360 distance, depending on your preference.

You might not have a password set on your account since it was created using the Google integration, go here to set one and see if you then can log in with email and password.

This is on my todo list!

You need to change the Multiplier 1 value to what you want to use, in most cases you can just use the same value as Mouse Horizontal Sensitivity

It is taking into account any discrepancy.

That's the accuracy of the robot I use to test, so if you can notice that you are literally more accurate than the robot
So no, you can't notice that. It doesn't hurt to get the sensitivity as accurate as possible though, but I wouldn't worry about anything less than a millimeter.

It works for everything except Gunner Aim Sensitivity (Look only, it works for Zoom) and Transport Vehicle Freelook Sensitivity.

Absolutely, this works exactly like with the scopes; you keep the same tracking speed.

This is the vertical movement (it has the same wording as horizontal, can be a bit confusing). The horizontal movement is 6.096 cm. To match the crosshair to edge movement to this, set the Windows / 2D conversion setup to MDH 100%: https://www.mouse-sensitivity.com/?share=edd8d784fe94306bef13d4810207d608
Advanced mode is selected here, so you can see in the bottom of the Valorant calculations that MDH 100% is equal to 3.0495 centimeters mouse movement as you want it