Well, technically speaking, if your C++ spins python instances, it's JIT as well. Not to mention that it might be generating and loading shared libs (or at least accepting some sort of signed injected shared libs) in order to deal with unpredictability of changing requirements. I am actually somewhat baffled that the same people who think that dynamically generated shared libs are clever can be the people who think that JIT runtimes are crutches.
Having said that, let me actually get to your point. Semantically, C++ is C + syntactic sugar. So, while it's not implemented this way (anymore), it can be. So can any other language which has a run-time similar to that of C. Once you allow for language costructs which call into the native C libs on a platform, your language is good to go to be pre-processed into C at compile time and than compiled with whatever compiles your C.
BTW, syntactic sugar is not an insult. Syntactic sugar is a Good Thing (TM). It allows to offload to machines work which would otherwise have to be done by humans.