My company uses haproxy managed by synapse extensively. As a developer I'm super impressed at how fast Willy Tarreau and co are moving and changing haproxy to

My company uses haproxy managed by synapse extensively. As a developer I'm super impressed at how fast Willy Tarreau and co are moving and changing haproxy to keep up with things like envoy and friends. One issue we have with our internal instances is that while the inbound sockets are passed across reloads, the connections/sessions state have to be initialized on every reload. We also use mTLS, terminated between services by haproxy itself on both sides. So we have some services using haproxy as a client side load balancer where there are hundreds of backends for the service and that list changes somewhat frequently triggering reloads. This leads to heavy CPU usage on all the backends who have to deal with clients reloading and re-negotiating mTLS sessions. I haven't been able to tell from the various marketing messages, but does the new data plane API avoid restarting the process, and hence this re-negotiation?