UW is happy to hand off Aggregate support at anytime.
It is important to note that Benetech's ODK Hamster is designed for the ODK 2.0 tool suite which is already based on RESTful APIs. ODK 2.0 tool suite is a RESTFul protocol vs the OpenRosa standards used for ODK 1.x Tool Suite.
My personal opinion is a fresh UI should be done that abandons GWT, so I am in agreement with Jakub. I also personally do not think Aggregate needs to support both the 1.x and 2.x tool suites (which will eventually be renamed) as I think a mirco-services approach using something like Docker is preferable. The advantage of micro-services is that deployers will be able to run the subset of the cloud services a deployment actually needs by spinning up only the components being used. It also makes it much easier to be modular and easier to mix and match services. It also avoids huge code bases like Aggregate which over the years has become harder for people to understand because strict modular design was not enforced. A micro-services approach is modular by design and since the various parts run in separate process it forces developers to adhere to a modular system.
As part of the ODK 2.0 Tool Suite release scheduled in September the new Sync-Endpoints for ODK 2.0 will be released. If you would like to check out the RC1 version of the Sync-Endpoints see the RC1 announcement for instructions.
Additionally, @linl33 is currently modifying a scaled down version of https://github.com/benetech/odk-hamster to be part of the Sync-Endpoint micro-service cloud that will replace the GWT UI carried over from Aggregate. The ODK 2.0 community is appreciative of Benetech's contribution and hopes to have integrated a portion of ODK Hamster into the Sync-Endpoint micro-service cloud by the RC2 release in August.