My theory would be that people are just trying to present alternate paths to "success," at least as far as they understand what you're after.
I haven't read all of this thread, but to be honest, it struck me sideways to begin with. I've tried it both ways - buy all the stuff, then learn to use it, versus learn learn learn, and buy what stuff I need to keep going. I prefer the latter, so all of the posts and vids I've ever seen about setting up a shop seem backwards to me. I might say "when you realize you need something to solve a problem you're working on, that's when you buy it." At that point you know enough to make wise decisions.
Such a sweeping generalization requires exceptions: you're going to need a meter, and a soldering iron. So... up front, but no need to get carried away. I've watched repair-person vids where that was ALL he needed -- that, and some brain power, a rather modest understanding of how the thing is supposed to work or what the schematic means, but a *very* good library of techniques for finding bad components, since that's nearly always what fixing something is about. We're not changing the design, here, just hunting for its... structural failures.
For a better understanding, more applicable to making stuff, maybe there are some analogies with software. Maybe if I wanted to help someone learn to design good code, I'd start with the basic behavior of the elements if the language - the components. Maybe start fitting them together in little fragments that do something useful, though not an app or anything. And build the smaller bits into bigger bits.
Maybe... well, what helped me in my early days was reading a LOT of code by others, lots and lots of it, and developing a sense of evaluating it: "this is good because..." or "this is bad because." But the enablement there was getting a stronger grasp of how to use lower-level pieces to make higher-level pieces; how to architect, and make good decisions. Radios have designs; those are made of sub-designs, made of components, architected at each level. If you're intent on learning, focusing on those things will help, with or without doo-dads on your bench. You kind wanna try get a library of sub-circuits on your mental self so you can look at a schematic and say, "ah... IF section, audio here... that's weird, what's that?"
I think tubes are great; we owe them a lot and they still have their places. Whether the expense is an issue is yours to decide; whether they are big and hot is not! But as a three-terminal device, or variation thereof... perfectly fine place to start.