Why assume python? It's huge compared to bash or perl. Lots of minimal configuration operational systems won't have python. More likely than go/ruby/node though.
And having a system using Python on startup is a pretty good indicator that Python will be preinstalled.
However, I see that the situation may be different in specialized distros.
Nevertheless, statically linked binaries are indeed a good alternative, and provide good-enough portability in a wide range of cases.
And from your list, Go doesn't really belong there, it outputs statically linked binaries. You can just plonk them anywhere.
This bit us in our ass with centos 6.8 , when another package required python 2.7... If you install 2.7 directly, your system fails with a thousand cuts. A chroot is needed for that, unfortunately.
As a general rule, never try to replace any program or library supplied by your distribution.
This installs it to /opt/rh, and you can run commands that need them with "scl enable python27 mything" or by sourcing /opt/rh/python27/enable in a script to set up PATH, etc.