This is going too far in the other direction. There are absolutely people who have mastered e.g. Java, CPP or whatever with language-specific knowledge. Being an expert on JVM internals won't boil through to Haskell.
Well, being a master of JVM internals does give you a very strong grasp on a very useful basket of concepts for GC and programming language implementations, so I'm not sure I would necessarily agree that there's no transferable overlap. But regardless, neither of these are applicable metaphors for a 101 level CS class—at the introductory level, you're better getting a broader survey of lots of different languages, because learning the transferable fundamentals is more important than learning the specific "trivia" of any particular language.
JVM is essentially project knowledge, if you're writing code that requires you to understand JVM internals really well, unless you're working on JVM directly, something is wrong within the division of labor. Programming with java requires no internal JVM knowledge bare the bare minimal surface ones (execution args, etc).
Why? If you're working on a performance critical application, you need that knowledge. Plenty of HFT firms use Java.
What's the reasoning behind picking Java for a performance critical application over something like C or C++?