Another issue on 2.4GHz is that half-savvy users set their channel bandwidth to 40MHz. Count it off--20MHz either side of Ch6 creates adjacent-channel interference on 2, 3, 4, 5, 7, 8, 9, and 10. That's just plain inconsiderate, not to mention that it also means all of those channels would interfere with that radio.
Why would a user set up a radio that by design interferes with 9 channels? Maybe if the nearest neighbor was half-mile away.
It's complicated - as a recovering member of IEEE 802, please accept my apologies...
That being said - in 2.4GHz - since probably 2014 or so, most, if not all, of the chipset vendors do opportunistic wide channels in the 2.4GHz band - e.g. if one asked for 40MHz channels, they might do it if the overlapping channel plus a bit to spare) could support it - e.g. if one was on Ch1+5, and 6 was clear for the moment, it would fire up 5 for a bit of a kick...
The bigger problem with 2.4GHz is that folks can go outside of the 1/6/11 scheme, and this messes up a lot more for neighbors in dense environments - consider apartments/condo's as a example. Someone there camping on 4 or 8 can create a lot of trouble for the adjacent folks following the 1/6/11...
Looking back - for consumer WiFi - instead of channel numbers, vendors could have done the low/mid/high (following the 1/6/11 scheme) and we would have been much better off...
From a historical perspective - 802.11 didn't always use 20MHz channels in the first place - 802.11 defined DSSS as 20MHz, but they also had frequency hopping narrow band (along with IRDA, if folks remember that stuff) - hence the reason why we have 11/12/13 channels for WiFi in the 2.4GHz band in the first place...
Along with 20/40MHz - 11g looked at a CNR of +20dB for co-channel interference - when we did 11n - that value changed quite a bit - -3dB, which means that even on the same channel, two strong sources, they need to perform the same...
Which helped out much for dense environments - but a lot of the press/blogs/forums, they still look at the 11g values...