Have sslEnabled be configurable on a per-cluster basis

We are migrating from couchbase community edition to couchbase enterprise. During the migration phase we need to have our apps be able to talk to community edition (without ssl) and enterprise (with ssl enabled) at the same time. Currently the sslEnabled property applies globally to all couchbase clusters and so we run into one of the follow scenarios:

1. have sslEnabled off everywhere and we don't reap the benefits of encryption talking to our enterprise clusters
2. have sslEnabled on everywhere in which case we see timeouts with the client trying to talk to the community clusters

Can we have sslEnabled be configurable on a per-cluster basis?