I looked at the UA when it first came out and sort of came to the same conclusion as you. it wasn't a good fit for an environment that was already "operationalized".
But some new features have been added and using the UA could be a viable option for a new environment and they've added a lot of accommodations to convert an existing one. The biggest being the ability to add custom variables to the Node and Tier names. While this doesn't mean you get to keep the existing familiar names that you already have, you don't have to make "1200 rules" for each one.
You can set up a rule for an entire application or one per tier.
One unwritten benefit is that the UA can be installed by the Unix/Linux team and you'd theoretically would never have to touch the machine. Everything can be done via the REST API Json calls. It will even add the correct params to the JVM start script.
There is up front work to getting this up and running, but once you've created a working library of rule books, it seems like decent single point for maintaining the environment.
... View more