I don't extend any remote services in the uber-buildouts, because I don't want to be dependent on a live internet connection for production deployment (this presumes you have a warm egg cache, of course).

plone.recipe.zope2zeoserver and plone.recipe.zope2instance do support repoze, in a sense. They're used in this setup. There's no magic repoze script or command runner in the build.

There's also a plone.recipe.repoze2instance, I think, that Hanno made.

The ZEO server side is identical anyway. The client side just needs a valid zope.conf, so really we could just generate that with collective.recipe.template.

Nice Buildout : ) I already use(d) HAProxy / Varnish its nice to have a comprehensive buildout to play with.
On a side note it may be an idea to put in lxml deps (python-libxml2 / libxslt-dev ) which it cant be built without which caught me out for a few mins..