OK, thanks. In that case, I'm going to compile the Linux binaries on Debian Stable. (Are they then also going to run on Red Hat distributions? Don't know... I've only ever used Debian, or Debian-derivatives, apart from some short stints with SUSE in 2001 and Arch in 2015.) I'll have to look into how to get the newest versions of Rust to run on Debian Stable.
Compiling my engine for the Raspberry Pi 4 is not an issue; I've already tried it. If the Rust version is new enough, it'll work. Assuming your statement above is correct, it'll then keep working in the future.
Under Windows, I use MSYS2. I a program compiles cleanly under Linux with either GCC or CLANG, it normally compiles under MSYS2 without issue.Then again, having an easy way to build from source also allows the compiler to optimise for the CPU of the system if using -march=native. A big difference to Windows is that building from source is usually difficult under Windows, at least compared to Linux.
Rust only has one compiler, and no make-files. Compiling a Rust executable should work exactly the same on any system. I actually use the Windows-version of Rust, but I compile using the windows-gnu toolchain instead of windows-msvc (difference: the first uses the GNU LD linker, the second the Microsoft link.exe linker); and I also compile using MSYS2 as a shell.