(Update, in further WSL research… because inevitably WSL lovers may start asking me questions here.)
I found out I could modify a file to add WSL support; google “PlatformIO WSL patch” which brought up this support reply. In theory it means I can go all-UNIX-paths. I’d still have to run the teensy-cli exe (still runnable from WSL back to Windows to install the .hex, so I can still install the .hex from a bash script, in a firmware upgrader).
(Clearly, Pros/cons. For stock PlatformIO upgrades, I’ll just stay non-WSL; just a bit annoying to switch in/out of Remote mode for my other projects versus this project.)
Also, a bit of extra big hoop jumping has to occur if you modify the USB PID/VID away from the Teensy standard, just adding this here. My project compiles at the command line under WSL, so that’s fine for now, as I have a backup command line build process. So it’s a workflow pros/cons thing.
From the github stuff I am seeing on PlatformIO it is my understanding that eventually a new verison of PlatformIO is coming out eventually that’s more prepared to support WSL remotes. Just adding an extra vote that I’ll be eager to anticipate WSL support once things settle down in the country a bit more. (Only learned that tidbit recently.)
On that note, I think I’m finally 100% fully set up, and can sunset Arduino IDE for almost everything except a vestigal install to provide the needed CLI stuff.