The plan
I'm thinking about making a reusable C++ build system implemented in both Bash and Batch, so that one does not have to install Python nor CMake, just to compile a project. In order to maintain the same behavior across different platforms even if someone makes modifications to the build system itself for all projects, it would be nice to have both versions generated from a single portable scripting language before distributing the source code with pre-generated Bash and Batch build scripts. Compiling a utility binary for checksums and other helper functions can probably be done as an automatic part of the build system, if the program is not large enough to depend on itself for building.
The long rant about C++ build systems
If you have ever tried to compile CMake itself on an ARM-based mini-computer, overheating for eight hours before crashing, you might understand the need for a lighter cross-platform build system. Using handwritten Make files is a major source of linker errors and crashes. Python keeps breaking backward compatibility, so you have to install a specific version. Whenever a build system has no official binary distribution for your system, you have to either take your chances with a download site full of malware or build it from source code using another build system, which is built using yet another build system, until you have a cyclic loop of dependencies just for calling the compiler with a few arguments.
The question
Is there a clean scripting language capable of transpiling to almost any system's pre-installed scripting language?
Fallback solutions
If it's not possible due to unwanted side-effects or name collisions, I can just translate my existing build system from Bash to Batch and read project dependencies and settings from portable project files listing source folders and linked libraries, or automatically compile a build system from a single source file before the project is built using it.