Odd clock stretching when WSL is installed

So kind of an odd issue, is similar to the windows defender bug.

So I have my 9900K at 4.7ghz, I've known windows to be a bit finicky with windows defender specifically real time protection which messes up effective clocks. When I have real time protection enabled, my effective clocks drop 50-100mhz lower than my core clocks (4700mhz) when under load. If I turn off real time protection the effective clocks stay pegged at 4700mhz, matching the core clock. So I've edited the registry to disable real time protection permanently.

Now I have Wsl2 installed, and noticed the exact same phenomenon, I removed wsl and turned off the virtual machine check boxes inside off turn off apps and features settings, so not sure if it's wsl or the windows virtual machine setting that does it.

So, any fix for this? I'd like to still have wsl on my system, but as I'm an avid overclocker and like tinkering, I'd like my effective clocks to be matched when under load.

Start by reproducing the reported effective-clock drop with WSL2 installed, then compare it with WSL removed and the Windows virtual-machine features disabled. Check whether Windows Defender real-time protection, WSL2, or the virtual-machine settings trigger the discrepancy; done means identifying the responsible component and documenting a confirmed fix or limitation.

Written by the indexing model from the issue text.