“WifiWave2 CAPsMAN only passes wireless configuration to the CAP, all forwarding decisions are left to the CAP itself - there is no CAPsMAN forwarding mode.”
Do you know if this is going to be implemented? The legacy Capsman was much easier, now we have to be defining the VLANs in each CAP, it seems to me that it goes against the spirit of having everything centralized.
Configuration and management remain central.
You can work around centralization of traffic using EOIP or whatever other tunnel.
(BTW that tunneling is basically the same thing which happened in old capsman)
As for VLAN, if you do not require any further ports on the AP to be managed via VLAN, you can simply set those devices in caps mode.
VLANs will be populated then via datapath settings. → forwarding via VLAN then.
Give it some time, I’m sure it’s some SW restriction to have the VLAN handling being fully functional again.
So are there chances that “CAPsMAN forwarding” will be added to CAPsMANv2 also?
If not, what would be the recommended approach to setting a CAP with multiple APs (main, guest, iot, etc) setup so that all traffic is handled on the CAPsMAN controller?
I would (and have 
) choose VLAN.
Especially because my IoT devices are not allowed to access Internet (which is a single line in the firewall).
I always used Local Forwarding.