The only safe way to use XDCR is if you have a single master Couchbase Cluster + Sync Gateway that accepts writes, and all of your other CBCluster + Sgw are read-only. (Sync Gateway doesn't currently have a read-only mode to my knowledge, not sure about Couchbase Server). Otherwise, since XDCR is not aware of the _sync metadata field in the documents, it will essentially corrupt documents.
Having said that, we've done zero testing of XDCR + Sync Gateway in-house so far, so you'd be in unchartered territory.
Another option is to try
sg-replicate, which uses the ReST replication protocol to sync between Sync Gateways in an eventually consistent fashion. You would be able to have all your Couchbase Clusters + Sync Gateways accept writes, but:
* They would be eventually consistent -- there will be a delay when docs make it from one cluster to the other.
* You might end up with document conflicts. Sync Gateway is architected to handle these gracefully, so they won't cause any issues, but there will be more work on your part to handle these conflicts in your application.
sg-replicate is still fairly alpha / POC, but has undergone some real world dogfood testing and seemed to work fine. Since most of the work is handled on the Sync Gateway side, it's a fairly simple tool that just shuttles documents back and forth.