Registering with the servers will cause the service to be associated with that server pod. If the server pod dies then Consul will assume all the services registered with that pod are also unavailable. If you’re using the service registrations then I think this won’t work for you.
If you’re only using consul-template with k/v values then talking to the Consul servers isn’t terrible with the small workload you have. Clients can help with scaling.
I’d recommend you re-architect your applications to work with a single Consul cluster. Then you can use our Helm chart and all the automation we provide.
Perhaps you could also look at Consul Enterprise which has namespaces. Then you could keep the same behaviour and each service could live in its own namespace.