From your quote:
> With a good driver scanning takes only a few seconds
A few seconds of not transmitting or receiving packets. This is in line with people having sudden several hundred millisecond ping spikes.
A few seconds of no real traffic is absolutely noticeable impact for constant, latency sensitive traffic.
> From your quote:
>
> With a good driver scanning takes only a few seconds
You omitted the immediately following text: "*and the driver breaks the scan into chunks*, returning to the associated access point’s channel periodically to handle pending traffic."
A good driver will return to the AP's channel _during the scan_ so that there is never more than (say) 100 ms of latency even while the scan is ongoing.
Yes, but good drivers can mitigate the latency hit by not scanning all the channels at once. https://blogs.gnome.org/dcbw/2016/05/16/networkmanager-and-w....
> Since you're not transmitting, it should be low-power,
Depending on the hardware/firmware quality, tuning to each channel can use a lot of energy. As for "not transmitting," this is true for passive scanning (generally preferable) but not for active scanning.
> but you have to tune the radio to each channel, so you can't communicate with your AP.
Right, but _if the OS and drivers are written properly_ (on both the client device as well as the AP ) they'll buffer unsent packets… the high latency during the channel changes is unavoidable, but the dropped packets and broken TCP streams are NOT.