Color calibration purgatory: Win10->nVidia->Monitor....all conflicting

Win10prox64/GTX 1080ti/yadda³...

Brief:

Got 3 calibration variables in the way for color correction. How to keep Win10 out of the loop as much as possible?


TL;DR;

Yes, this is a Win10 question, ANAICT.

Ok, I'm yet another person struggling with the color of a TN panel monitor (Dell S2417DG). The monitor is in all ways spectacular, and one of the few 24" 1440p monitors out there.

However, the color desaturation inherent in TN monitors is a deal breaker, and I'm trying really hard to calibrate this thing to raise the colors out of "washed out". This particular TN monitor is known for having this problem, so I have to be careful.

A HUGE WRINKLE in all of this however is that I cannot figure out how Windows 10 handles its own calibration scheme. As near as I can figure out, it does this entirely before the nVidia drivers get ahold of it. It doesn't seem to directly teeth into the nVidia drivers themselves by "asking" it to adjust the settings for it.

So: If I use the windows 10 calibration wizard and modify the Gamma control, I now have the following:

Win10 Gamma ---fed to---> nVidia Gamma ---fed to---> My monitor's Gamma

UGH! Is this right? This is akin to having a tape-deck ramp up its own volume and feeding it to an amp which feeds to a speaker with its own volume control. Let's forget about games that try to assert their own calibration hooey for the time being.

Is there a way to neutralize the Win10 settings to kind of "baseline" that allows me to keep it as far out of the way as possible so that nVidia calls the shots so that I can have only 2 variables in the way?

TIA!