Going down a different containerized route, if you use Docker for this you won't even need a separate WSL installation for each project but you'll still get your own container based isolation with an "open terminal and start coding!" work flow.
WSL plays nicely with Docker for Windows[0].
At this point Windows running Docker connected through WSL offers me a more productive Linux development environment than running Linux natively (mainly because certain apps I depend on don't run on Linux).
I've been running this set up for months and it's super solid.
I really like your blog layout/theme. Clean and readable. Have you tried mounting code from WSL into a docker container and using vim/emacs in a shell in docker?
I keep my source code outside of WSL's file system because I don't trust it yet.
It's then mounted into WSL and Docker for Windows. Docker volume mounts work fine with that set up.
I don't use vim/emacs but running them straight in WSL should be fine. I wouldn't think to run vim/emacs directly inside of the container (because I try to adhere to the "1 container, 1 process" best practice) but in theory it would work no problem.
In this WSL set up article[0] I go over installing Sublime Text within WSL and using MobaXterm as an X server. It runs lightning fast.
WSL plays nicely with Docker for Windows[0].
At this point Windows running Docker connected through WSL offers me a more productive Linux development environment than running Linux natively (mainly because certain apps I depend on don't run on Linux).
I've been running this set up for months and it's super solid.
[0]: https://nickjanetakis.com/blog/setting-up-docker-for-windows...