Uh... objc is probably possible but all the other stuff is not likely to have a good backing. We're talking of inside the kernels/on device, nothing about the runtime api - restricted subsets of python and other things are possible but its clearly a different environment. It probably wouldn't be an easy task or ever properly supported and the language will be very different from how you know it. Taking C 7 days a week over C++ is flamewar words (akin to my earlier statements) but I put it in the same basket as someone who thinks goto is evil... you don't or are unwilling to understand how to use a tool that can help you. I'm not saying its not rediculously over complex but if you understand how to work with the complexity you will produce faster code than C, and it will be more adaptable/reusable - if you don't understand why go study why this is true. Remember also we're side skiping out on all the issues that embedded folks hate too: no virtual anything, no exceptions, no dynamic stuff. Just classes/structs and the full power of templates and type traits. This actually also has the effect of making reusable constructs but allowing you to tune them to your needs... on the kernel/device side.
Maybe have a look at CUB to understand practically (through a popular library) why all this is a good thing.