We wanted to drive Aminator from Jenkins in the end. Our original goal for the rewrite was to do something similar to what you suggest. Aminator would have some kind of job manager backed by something like Celery, web front-end that used the back-end ReST API, etc. After mulling it over, Jenkins seemed like a better fit for us and simplified a lot of the architecture.
That said, just mulling it over, taking Aminator's core and wrapping it with something like Flask or Bottle might not be too difficult...