Netconf connector not safe in 3-node cluster

It seems like odl-netconf-connector-ssh feature in Beryllium (and Boron) is not ready for cluster deployment, as it can lead to "server unhealthy" error state.

See [0] for recent example, where the reason is:

2016-01-22 10:54:10,205 | WARN | lt-dispatcher-18 | SimpleShardDataTreeCohort | 154 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.SNAPSHOT | Store Tx member-3-chn-2-txn-1: Conflicting modification for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[

{(urn:opendaylight:inventory?revision=2013-08-19)id=controller-config}

].
2016-01-22 10:54:10,206 | ERROR | lt-dispatcher-44 | LocalThreePhaseCommitCohort | 154 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.SNAPSHOT | Failed to prepare transaction member-3-chn-2-txn-1 on backend
OptimisticLockFailedException

{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}

Of course, there is odl-netconf-clustered-topology feature to be used with cluster, but that does not initiate the self-connection (controller-config device) that is needed for users who want to re-configure ODL in runtime using restconf.

Is there a way to use netconf-connector functionality in 3-node cluster?

[0] https://jenkins.opendaylight.org/releng/job/controller-csit-verify-3node-clustering/54/consoleFull