This is a great example to keep in mind against the high praise WSL receives— not because it's particularly dire, but because it's representative of how surprising (and basically intractable) WSL issues generally are. The product is chock full of bugs like this which will only impact a small subset of users, but which are showstoppers for that subset. (Some of them can be worked around, but good God are they a PITA.)

They tend to be issues that 'seem' advanced, but the missing functionality is usually something that the vast majorities of developers who have run a Linux desktop for development would take for granted as a possibility.

You're you saying if I ssh into windows and am dumped into powershell, I'm unable to type wsl to drop into linux?

Yes, that is the case when you upgrade to the current version.

Bummer, but at least it's described as a "known issue" and the fix appears to be in progress.

This hack might help some: https://www.hanselman.com/blog/how-to-ssh-into-wsl2-on-windo...