For the work part in particular, you may find that a virtual machine will get the job done pretty well. With modern CPUs there's basically no overhead, so it's often easier to just run the OS you need in a VM.

You can just run it in the background, run your .NET and SQL server and stuff, possibly VSCode remote into it. PowerShell over SSH. If you need to run a GUI application, you can just RDP into it. FreeRDP has a cool feature where it can RDP a single application so it pops up as any other app on the host. Works great when you just need the database's GUI or whatever.

With virtio drivers and everything, it will be essentially as fast as if native. GUI will be slow because of software rendering, but the point is to use it as a server and only use the GUI as necessary, and for server stuff RDP isn't too bad given it's basically localhost network.

There's also the fun but painful world of VFIO and passing through a real GPU into the VM and feeding back the video to the host with Looking Glass. It's so good you can game on that (anticheat still won't work though, they don't like VMs), so if RDP bothers you that's an option. Although in my experience, Visual Studio is just as slow and buggy natively, so I wouldn't bother and just RDP.

If you add virtiofs to the mix, in theory you can share the code folder and use VSCode on the host and compile on the guest, or even compile on the host and run on the guest. Or send compile commands to Windows over SSH from VSCode. I have my entire Steam library (and Proton containers) on virtiofs and it works perfectly, so I have to imagine a code project should work nicely as well.

Virtual machines are an awesome tool. There's also the benefit of keeping all the work stuff in a big isolated container. If you have multiple projects you can make multiple VMs and not worry about one project needing version X and the other version Y of whatever.