Multi-DB as a multitenancy solution

I'm wondering about using Multi-DB as a solution for multitenancy. I'm exploring a project where every site on a multisite install would require its own unique database. I'm looking at it as using Multi as the application codebase, but having Multi-DB to manage the data for each client.

The use case requires an independent database for each client for security and segregation reasons. I'm think about this for ease of management over using ManageWP to handle control of everything. All the sites on the network will have the same themes, plugins etc, but the data needs to be distinctly segregated and locked away from the other sites (segregated database servers may even need to be required - this is an enterprise level project).

Any thoughts on how flexible Multi-DB would be as a solution for this?