Consider passing Windows environment variables down into WSL so the user can set environment variables in Windows and imported commands will honor them about powershell-wsl-interop

[mikebattista]

Introduced support via $WslEnvironmentVariables["<NAME>"] = "<VALUE>" rather than try to send all Windows environment variables down.

This neatly contains WSL environment variables separately from Windows environment variables but also avoids conflicting with variables like PATH that are automatically modified and set within WSL.

Furthermore, many Windows environment variables point to absolute paths that would need to be translated to be meaningful within WSL, so opting in variables vs. trying to send them all down avoids the overhead of trying to translate them all every time a command is called when most of them would not be useful.

[mikebattista]

Note that if you don't mind cluttering your Windows environment variables or already have some set defined that you'd like to share within WSL, you could also use the WSLENV environment variable.