One thing is that if we're going to have different languages interacting then the language that will make this happen is C.
Additionally, robowaifus are cutting edge tech, so we won't be able to cut ourselves some slack with convenient off the shelf hardware and operating systems, we'll have to deal with purpose-built hardware and software which inevitably comes with odd behaviors and optimizations, and to create and make use of those knowing the theory behind assembly is required, so that when the hardware pops up an assembly programmer will already know all about memory models and vector instructions and whatnot and be able to pick up programming for this new hardware with just an instruction set listing.
Why are soundcards cheap? Because inside them is a DSP with a native word size of 24 bits and which can only read and manipulate data in that one size, it also has weird instructions that optimize reading an array in an unusual order common in DSPs, not a full-blown ARM core that's made with many more millions of transistors providing features a soundcard will never use.
Similarly, the average router until recently had a MIPS CPU with no floating point unit, floats aren't relevant for router tasks.
At this point the whole range of programming languages is required somewhere. Straight up machine code, compiled languages, and scripting languages.
Focus on theory, general experience, and topics related to robowaifu engineering. Whatever you know will likely be of use somewhere.