I think the issue is that CAPsMAN is not really a management layer for an abstracted WiFi device, but just a tool to copy a block of configuration data from the local device to the managed devices. That is why you also need to install the WiFi drivers on the CAPsMAN management device, even when it is not running WiFi at all.
With the new drivers, the configuration block structure is completely different, and everything had to be replaced with a new version.
So there is no chance of the new version managing old devices. When that would have been practical, they could have done it already.
I am running a managed WiFi system from a similar company (the one named U*) and there it has been done differently. The management software manages devices of different generations and chip manufacturers. The configuration data is distributed as JSON files with generic parameters and their values. Each device receives its properly prepared JSON file (from the settings you made on the controller) and configures accordingly.
But the whole thing is much “heavier” than the MikroTik solution! The controller is a Java application that becomes larger all the time, I run it on a virtual machine with several GB of disk and main memory. That manufacturer originally supplied a small Raspberry Pi 1 like device that could run the controller, but over time it became more overburdened with it and it now no longer works, you need a new more powerful device (more memory, faster CPU).
The wireless APs also are much beefier than typical MikroTik units, with the associated price. MikroTik has clung to their 16MB flash while these APs had 256MB or 512MB flash for a long time. So lots more space for nifty data-conversion agents on both sides.
So no, I don’t think this is going to happen. Unless MikroTik makes that proposed “controller application” (which would be running on a powerful device) working at some time. See http://forum.mikrotik.com/t/mikrotik-devices-controller/158354/1
But I would not hold my breath…