CMA-compliant KMs do not necessarily be mapped back to standard configuration variables. When you look at the configuration, you will notice that there are /ConfigData variables and in some cases /RunTime variables.
However, you can add your not CMA-comliant KM in the Configuration Variables section of the Monitoring Policy by setting the /AgentSetup/preloadedKMs variable. This will be merged with the /ConfigData/preloadedKMs.
I believe certain variables are common between CMA-compliant KMs and custom KMs. For example, /AgentSetup/preloadedKMs. I believe the /ConfigData tree is used to manage configurations that are emanating from CMA. However, I believe that they map into standard Agent configuration variables. Is that not true?
Also, if you’re currently using PCM, it is difficult to move from PCM to CMA because PCM offers a number of provisions that are difficult to emulate in CMA. For example MERGE and APPEND. Also, the fact that Agents can be included in various groups in PCM, gives you the ability to easily create a configuration that’s based on a composite configuration results from applying ApplyOnNew and ApplyOnApply rules from the top down in the navigation tree. I don’t see any easy way to replace that. I mentioned that in a separate post.