To tie the above to this particular thread, just the other day I stumbled into another serious WSL2 issue wrt. Microsoft's current "Linux" support: DNS issues. In short, the WSL2 DNS component completely fucks up some name lookups. In the case of "baidu.com", it inserts the results for "nsX.baidu.com", causing e.g. getnameinfo() C library function call to provide those too as the results for "baidu.com".
More annoyingly, WSL 2 doesn't support mDNSResolver which after like forever MS has finally decided to support.
And most annoyingly of all, WSL 2 can't use USB devices. Otherwise it would be useful with openocd. Thankfully Linux in a VM works spectacularly well.
WSL 2 also makes running various python utilities a breeze - like InteractiveHtmlBom or KiPart. Installing python eggs or running setup scripts just never seems to work natively on Windows.
The new terminal is usable. Not great compared to say iterm2 on Mac - but usable.
PowerToys will swap caps lock and ctrl. Who uses caps lock anyway? The only reason I found to have it mapped to a key in the first place is so I can actually disable it after some asinine installer has turned caps lock on - and left it on.
I miss MenuMeters. The real thing. MeterX... meh.
TaskBarX with translucent task bar... works well and looks nice.
Installers LOVE to drop shortcuts on my desktop. Why would I want application shortcuts on my desktop when I can pin them to the task bar, or add them to the launcher/tiles shown by the windows key?
Windows' automatic GPU switching often doesn't work.
The exact same python programs start up and run significantly faster in WSL 2 than natively on the host. Operating on data hosted by Windows no less. That says just about all I need to know about Windows' page caching, VM system, shared library mechanics, and scheduling.