Programming languages are to programming what foreplay is to sex - important but not the main exhibit, my point being that Python and (especially Go) are relatively simple languages coming from your background so you could realistically learn all 3 in a few months if you really wanted to.
A curious C++17 programmer, how does Rust teach you much about "how computers work under the hood?" I thought Rust wrapped most of the ugly bits in 'unsafe' and tried to keep programmers from them?
I'm not a rust guy myself (Fascinated by the memory/thread model but totally disinterested in the rest of the language) but to understand rust (or C++, D, blah blah) you do need to have some concept of a how a computer actually works. The really ugly stuff is hidden but in order to actually do work (thermodynamically rather than REST apis) you need to know what your code actually does (or acts like?)
"Under the hood" is far too complicated to learn from programming as soon as you go below the surface.
If you care about work opportunities - Go, and it's not even close.
If you're experienced in Rust, what problem spaces are associated with Rust stacks?