Possible solution for name conflicts

[ethanparker436]

As an example, the readme mentions conflicts:

coreutils/README.md

Line 61 in bc282d5

| `expand` | 🛑 | 🛑 | Conflicts with the built-in DOS command |

The expand command appears to be a utility located in:
C:\Windows\System32\expand.exe

Solution: Ignore variables and encode the file address inside the source code of cmd/conhost.
Example: %SystemRoot%\System32\expand.exe

Any legacy *.bat or *.cmd file is executed by cmd/conhost, without breaking anything.
Newer shells can use posix expand by calling it through the PATH variable set to a different directory.

In this case, it would also be useful to create a bash.exe file that executes sh scripts, uses bash syntax, and only calls these coreutils.