I can defiantly name 5+ times in recent memory where a scope would have been useful. i know exactly what i would have measured and how i would have set it up. what im not sure of are the mistakes i would have made along the way and what the results would have been. All the cars im thinking of did get fixed and customers are happy. I do think the scope could have prevented a couple comebacks and saved some time though. I have attended several classes that went over testing methods and setups using scopes but i really am better off struggling a bit with something new, maybe even failing in frustration and letting that drive me to learn what i have done wrong. i never forget lessons learned that way. I have a quality dmm, a power probe, an amp clamp.... stuff like that. Im not totally new to electrickery but its an area i need to build more skills in for sure.
I started using scopes in the automotive field over 30 years ago when the idea of using them for anything other than ignition was fairly uncommon. My first scope that wasn't on a cart was a Fluke 98, which I still have today. The first case that I remember where it saved me from a major headache is when I was given an an older Chrysler New Yorker (318 V8) for a tuneup and carb adjust/overhaul as needed. The complaint was hard start and rough run when cold. It was the cranking compression test that showed 3 bad valves that very quickly convinced the service manager to revise the work order. If I had just said "I think it has a mechanical problem because it sounds uneven when cranking" I probably would have been told to just do the requested work first. The Fluke 98 has a reasonably good array of special features that were very helpful in those days. OBD data has improved, ECUs are smarter and I actually think there is less occasion to use a scope these days. Setting up those specific tests can be done with a generic DSO but you'd really have to understand what you are doing.
If you get a regular scope as you indicate, how would you use it on a road test? One of the most useful features of a scope with a recording feature is to solve the "what fails first" problem when dealing with intermittent issues. Perhaps I don't know the specific issues that you encounter so that's why I asked.
Some specs seem redundant. Wouldn't sample rate mainly dictate how much resolution you could see on a given waveform? Also dictate the bandwidth the scope could be useful for? Also dictate how fast a rise time you could measure? But they are all separate specs. I'm missing something I'm sure of it.
Sample rate will set an upper limit on bandwidth, but BW can be (and usually is) less than this limit due to analog circuit design and marketing. BW and rise time are correlated but not always in a simple way. Both are essentially irrelevant to your application. The Fluke 98 has 20MSa/s and 5MHz BW. Anything more than that is "enough".
I asked before -- are you a member of iATN? If not, I'd recommend you have a look. I see you answered 'no'. That's the wrong answer! Given what your goals are--immediate and future--it would be insane to ignore that valuable resource. It's unfortunate that the waveform library isn't in the free section (it was all free two decades ago...) but you can get additional answers--and probably more relevant--to your questions in the forums.