TL;DR:
If you have awdl0 enabled on your Mac and see events in your Mac WiFi log while "the command" below is running, then you are likely still a 'victim' of the awdl0 SCAN (which is a disruptive, latency-inducing channel scan 
).
The Command:
tail -f /var/log/wifi.log | grep 'SCAN request received'
It's a good question. I can't say for sure on MacOS 14, but I'm running MacOS 15 betas and I don't see the same behavior as I once did when awdl0 was enabled. I hesitate to say it's fixed because it's hard to know what MacOS versions everyone is using.
But if you have awdl0 enabled and don't see the behavior and/or log messages I described in detail here (back in 2020, no less 
), then it's probably safe to say you're running a MacOS version where the behavior has been corrected.