yup except that when you expect a 50-100MHz 1GSps scope to show good fidelity on 1-2ns rise/fall time, then its just ridiculous.
It would indeed be ridiculous.
But for reasons best known to yourself, you have chosen to ignore paragraph 4 in the first post "The first point...". Hence your point is a strawman argument.
Yes, but if you're talking about a modern microprocessor (hey, those were your words, not mine

), then you're talking about a GHz-level device. Even your 350MHz analog scope isn't going to be capable of dealing with one of those.
That's incoherent technobabble; clearly something has been lost in the translation.
I think we're all in violent agreement on your main point: choose the right tool for the job.
What we're
not in agreement about is whether or not your example shows that an analog scope with higher bandwidth is a better choice than a digital scope with lower bandwidth for a
beginner to use with digital signals. Yes, the analog scope can
theoretically show the problems with the signal integrity of your example, but
in practice it will be difficult (
very difficult, I'd wager) for a beginner to use an analog scope for that purpose unless the glitch itself is
very repeatable (i.e., shows itself many, many times per second). Put another way, for digital signals, the analog scope is probably
not the right tool for that job, even if it might have enough bandwidth.
Absent those very specific conditions that make the analog scope workable at all, the real takeaway here is that if you are working with signals where the pulse rate is in the tens of MHz (more precisely, where the bandwidth requirements of the signals are high enough that the bandwidth or sampling rate required to see glitches would exceed what the scope is reasonably capable of capturing), then you need a scope with greater bandwidth and sampling rate than the entry-level scopes that are typically recommended. And guess what? It also means that you have to start worrying about probing techniques and other things that most beginners haven't even considered.
But if you're really working with such signals, chances are high you are
not a beginner! Or, if you are, you're probably (way) over your head, because if your signals are that fast, you'll probably have to go to extra lengths to avoid signal integrity issues in the first place, lengths that you wouldn't even have to think about with hardware typically used by beginners, and you'll have to go to extra lengths to ensure that, firstly, your probing methods aren't introducing glitches into the signal and, secondly, that they are appropriate for the signals you're trying to evaluate.
What this means, of course, is that one of the recommendations that must be given to beginners is that they work with relatively slow hardware, precisely because doing that would allow them to concentrate on things other than how to avoid the problems introduced by the transmission line characteristics of signal carriers -- and would allow them to use breadboards and other convenient prototyping mechanisms, to boot.