Much better results by only controlling external radios.
Yes I can see your point and it was the main reason why I have written this post, to understand whether there was any limitation from CAPsMAN vs direct config of each individual AP.
For me, in order to find out the settings needed to achieve the radio setting that I wanted, I had to play directly with the radio, where you can fine tune all parameters.
After that, it was also good to see how easy and scalable CAPsMAN was to define all sub-section with channels and several other parameters.
In term of easy organisation and single point to check the entire setup, CAPsMAN is good as you can provision easily your config.
I had added a 4th AP, only 2GHz and I removed from one dual-band the 2GHz channel to be assigned to this new 2G only AP. I did it with CAPsMAN, by just changing the MAC address of the provisioned AP and all the settings have been transferred to the new AP.
This is good and I guess invaluable for large networks (mine it's just 4 APs, so equally simple to maintain as manual config of each AP) where the centralised provisioning can make a big difference.
However as all centrally managed solution, if you loose the CAPsMAN router, all of your WiFi managed network collapse and you either restore CAPsMAN or reconfigure each AP manually.
I can see the value for CAPsMAN, I can see its limitation and the needs for wise implementation on large scale if you don't want to face issues later on.
But as usual it's good to have several options, learn from them and then decide what's best for you.