And, you could also wrap all %PATH% variables with quotation marks in scripts/env.bat like:

echo ";"%PATH%";" | %FINDDIR%\find.exe /C /I ";%WINPYDIR%;" >nul
if %ERRORLEVEL% NEQ 0 (
set PATH="%WINPYDIR%\Lib\site-packages\PyQt5;%WINPYDIR%\Lib\site-packages\PySide2;%WINPYDIR%;%WINPYDIR%\DLLs;%WINPYDIR%\Scripts;%WINPYDIR%..\t;%WINPYDIR%..\t\Julia\bin;%WINPYDIR%..\n;"%PATH%";"
cd .
)

Now my chronic system path problems solved.

@echo off
call "%~dp0env_for_icons.bat"  %*
if not "%WINPYWORKDIR%"=="%WINPYWORKDIR1%" cd %WINPYWORKDIR1%
"%USERPROFILE%\AppData\Local\Microsoft\WindowsApps\wt.exe"
exit

the other one is more complex, so not feeling it

@stonebig I didn't write all detailes of the second one, but it's about another "spaces in user path" related problem. In my env, both powershell and command prompt returned "cannot find" errors for executables located in windows/system32, such as nvidia-smi.exe which is frequently used for cuda users. I didn't know the cause before I find the solution for WinPython_Terminal.bat. After replacing %PATH% with "%PATH%", problems were solved. like:

set PATH="%WINPYDIR%\Lib\site-packages\PyQt5;%WINPYDIR%\Lib\site-packages\PySide2;%WINPYDIR%;%WINPYDIR%\DLLs;%WINPYDIR%\Scripts;%WINPYDIR%..\t;%WINPYDIR%..\t\Julia\bin;%WINPYDIR%..\n;"%PATH%";"

I had build issues trying the code change, so reverted till further courage.

Since Windows Terminal can now be configured to be the default console on Windows 10 and Windows 11, I think this feature can be dropped at all.

If one install the latest Terminal, he can set his preferences on his own.