More of the same thing jlawitzke wrote above,
If you are storing operational data in the ConfD CDB Operational Datastore, instead of or in combination with registering your data provider applications with ConfD, you should use the CDB API to set the data.
The ConfD MAAPI is for acting like a northbound client connecting to your devices / virtual instance over NETCONF, REST, CLI, JSON-RPC, etc. Here the client read out the operational data (statistics, monitor data, etc). And of course to set configuration.
MAAPI is sometimes used by the application for validation or transform implementations.
The ConfD CDB and DP APIs are the primary APIs for most use-cases where the application subscribe to configuration updates, read configuration, provide operational data or, like the use case we discuss here, push operational data into the CDB operational datastore (configuration use running, candidate and startup datastores).
So for reading config data from you application you will in the normal use-case read using the CDB API, for pushing operational data into CDB oper you would use the CDB API but with a different socket. And/or if you are registering and application data provider you would use the DP API. Hence, at least two sockets or more are needed.