may be you missed the point - in WSL, you are with Linux/unix based env. So your Vim or other editors and tools just work like in regular Linux, Windows part until needed can be invisible and uninvolved.
Other tools like VSCode IDE, has special handling (extension) to work _inside_ WSL and only keep GUI frontend on the Windows side (very close to how it works over SSH).
On the other hand, I quite often use "explorer.exe ." inside WSL to open File Explorer and jiggle around with files downloaded/created/modified (say with sed) in WSL and it works fine too.
Or use MarkText markdown editor on folder inside WSL being some git repo and I'm adding docs/instructions there.
I'm using WSL since about 2017 on insider builds and wsl1 for occasional cases and WSL2 as as daily driver for, 5 years, so nice for me and no need in Linux on desktop.
Other tools like VSCode IDE, has special handling (extension) to work _inside_ WSL and only keep GUI frontend on the Windows side (very close to how it works over SSH).
On the other hand, I quite often use "explorer.exe ." inside WSL to open File Explorer and jiggle around with files downloaded/created/modified (say with sed) in WSL and it works fine too.
Or use MarkText markdown editor on folder inside WSL being some git repo and I'm adding docs/instructions there.