I would worry less about _trigger jitter_, especially for relative measurements, because unless it's one of those toy scopes, trigger jitter will be negligible

I would worry less about _trigger jitter_, especially for relative measurements, because unless it's one of those toy scopes, trigger jitter will be negligible for this purpose, so yes the scope, but less trigger jitter and more measurement jitter. For anything that involves a scope, I think it's good practice to specify how and what you are measuring - namely what termination, what trigger level and show what the pulse actually looks like on the scope. Where you are definitely right is that all those devices can produce completely different looking pulses, and only by looking at the pulse with a scope that has sufficient bandwidth you can pick the right trigger level that lands at a point of the waveforms that gets consistent characteristics, namely you stay away from the top of the pulse and tend to trigger somewhere mid-ramp that looks clean, and keep your paws away from those AUTO buttons! ...but this is all nitpicking as far as the post goes, this is where lots of electronics people get triggered (badum, tss!) where we have a network in the middle that is, essentially, chaos.