FWIW - for 2.4GHz - I would keep things clean and simple...
20MHz channels
Disable Beamforming
Disable Turbo/Nitro QAM (sometimes mentioned as speed up to "up to 800Mbps"
Mostly because inconsistent implementations of features outside of 802.11n across different vendors, and this applies to one's own WLAN along with neighbors that might overlap.
One does get a bit of range extension with 20MHz in 2.4GHz with most radios - it's modest, but 2-3 dB can help between being attached or not.
There are some advantages to 40MHz channels in 2.4GHz with AP's that are standards compliant - e.g. "20/40 auto", as they really are "20+20" and the secondary channel is used only when that channel passes the clear to send processes defined in the IEEE spec - the problem is the older AP's that were "Draft 802.11n", but most of those have aged out and have been replaced.
See my post regarding Google Fiber insights there...
With Marvell based chipsets - I've found that in 2.4GHz, they work best in 20MHz, b/g/n-mixed mode, and pick the channel - and then they work extremely well - even across client chipsets that may support extra features outside of the standards (thank you broadcom..)