And as you get truly senior you've picked out the stack you like best out of the ones you've tried, the stack that lets you do anything you want to do with the least friction for your own personal style. And you realize there's little value to always being on the treadmill of replacing skills to swap their various pros and cons while your overall capabilities don't grow.
As I interpret it, it mostly is a graphical representation of what's related to what. I don't see anything wrong with that goal. If you mean the sheer quantity of the possibilities will scare people away, then that may not be a bad thing. Software is growing into a messy conglomerate of technologies where each org selects what to put on their own stack(s). One must be aware of that nature of the biz because it's not growing simpler.
In the old days, the big vendors gave you a tool-set and you mastered whatever that gizmo was. Those days are probably dead. Most modern programmers are multi-sub-gizmo gluers.
As a sales tool for STEM, yes it's bad, but it's good as a reality-check about the industry.
True, but it's helpful for a junior to know the lay of the land even if they don't know how to use every one of these technologies. It does a junior no good to keep their head down and focus entirely on PHP, then when they look for their first job they find all the listings want React (not saying there aren't PHP jobs)