No, it gives you
exactly what you want, which is how fast the scope completes a given number of averages. So if you are playing with your DUT, it tells you how quickly the scope will respond to a signal change while doing the averages. Or if you want to save the data, it tells you how long to wait until you can hit the stop button.
The waveforms per second (if the scope has a trigger out and one has another scope nearby to measure it) do not necessarily correspond to the number of waveforms averaged, as seen in a couple of examples above.
Now, there was a test done earlier on another thread with 3000T scope:
I made a test with my 3000T.
3 ns pulse with 10 kHz repetition rate. at 20 ns/div, normal ACQ mode, on trig out full 10 kHz.
BUT, if I set average ACQ mode, it is STILL 10 kHz....
It seems to be doing running average. Meaning, there is no slowdown in acq rate, but latency in result after change.
Latency will be proportional to number of averages and timebase, of course.
At 200 ns/div normal ACQ, trigger rate is still 10kHz, but average ACQ drops to 1.7 kHz (at 1024 averages)
So there is a slowdown here.
It is highly dependent on settings. If OP would give exact settings, I have no problem running scenario to verify exactly how fast 3000T would be.
But all it says that the scope can average at more than 10 kHz,
assuming the trigger out equals to waveforms averaged. Increasing the ns/div scale will necessarily slow it down, both because of longer acquisition time and possibly because there are more points in the waveform. Increasing the trigger rate until it is much higher than waveform/sec speed would tell what is the maximum speed.