I think you're looking at this from the wrong angle. A MSc is not supposed to teach you programming languages, because whatever you learn now will in any case be obsolete in 10 years. It's supposed to teach you fundamentals and how to think, which is timeless.
One of the most famous introductory CS courses in the world, MIT's "Structure and Interpretation of Computer Programs", was for decades taught using a programming language called Scheme, a dialect of Lisp that's wildly different from any mainstream language and is used for basically nothing other than this course. This was partly intentional, since it does a great job of shocking teenage hacker wannabes out of their "I already know language X so I'm hot shit" complacency.
So tech is a lot like crossing a river hopping from rock to rock. You make these leaps, and you try (or mostly hope) these leaps lead to a great career.
At the beginning, you're a 20-something person. You mostly don't get to pick your steps, especially if you're in the employed-by-others track.
Standing in the river on my rock, at this advanced career stage, I'm certainly not looking to "learn programming languages". That was long ago.
Right now it's all about picking the next leap based on the conviction that it's going to be a great ride in the future, which is much closer to sunset for me than most in this forum.
One of the most famous introductory CS courses in the world, MIT's "Structure and Interpretation of Computer Programs", was for decades taught using a programming language called Scheme, a dialect of Lisp that's wildly different from any mainstream language and is used for basically nothing other than this course. This was partly intentional, since it does a great job of shocking teenage hacker wannabes out of their "I already know language X so I'm hot shit" complacency.