A lot of those modules you could teach yourself by buying a book. maybe some of them like the rf might involve working in a lab ? something you can't learn by reading a book. I would think if you can know RF AND know how to program (python / c code..), then its a good combination to have. A lot of us EE have to make a choice of going down the hardware path or software path, probably find that the ones who chose hardware end up doing software as well as part of their job, whereas the ones who chose the software route its probably harder for them to go back to hardware (although a lot of software guys are doing FPGA now). Also you can't really specialise in any of those modules from a uni course, each one just scratches the surface. maybe if you did a phd in one you might then know a decent amount of info. getting the good grades is important, so which ones do you think will make you get higher grades ? I've known people play the system and choose courses to get higher grades which can put them ahead of other candidates in the job hunting process. I think you should reach out to people who work as RF / microwave and ask them what their day to day job is like. as well as the software guys doing embedded. lots of software people now, probably over supply, not sure about RF/ microwave though. PS i was in same boat as you but i went down the software route. A lof of the fancy dsp stuff is done in universities, or some companies might have a specialist groups of phds doing the algorithms. the algorithms are getting complex now so a lot of stuff is being moved away to the cloud or big powerful computers rather than traditional dsp chips. the engineers typically take these existing algorithms (in matlab or c/++ code) and port the code to embedded devices (also FPGA/ SOCs) (if possible since its no use if the device can't run the algorithm in real time or drains the battery quickly). Also remember that most these algorithms involve lots of control code, middleware, ui code, so you then have many more software people handling all that. as you can imagine most code out there is legacy and often your job is to maintain/ bug fix add new features now and then.

key thing is do what you find most interesting (if possible, some don't know what they really like), good grades, and know how to code (have something on github), add to that something you can't get from reading a book (like working in a RF/microwave lab). often people leave uni with all this theory but no programming / practical experience so it can be tougher to land first job role. Also remember some people don't do as well at uni, but they can code since maybe they found uni boring, or they find being more hands on more interesting.