Currently if you click on deactivate for the CAC editor page only the editor page itself is gonna be removed from the publish but not the connected configurations. The editor should provide a possibility to remove existing CACs.
This is related to WCON-62. A UI exposing the underlying config node structure including their metadata which allows to also activate/deactivate individual configs would be nice.
yes - if we find a way to display the (individual) publication status for the related context-aware configuration entries (which may be a lot), it would be a simple step to add a button do activate or deactivate them individually, as supplement of the current concept using the reference provider, which helps only for activating the configurations.
in my pov the first problem is a "UI" problem - how to display this lot of information in a useful and not overwhelming way. perhaps in an extra dialog or expandable. getting the information for the configuration is not that hard, we have the building blocks together already.
What about a custom Granite console on top of /conf (with some filters in place)? There is an example for that in https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/customizing-consoles-touch.html.