To answer my own question: The proposed hybrid approach was abandoned due to the complexity involved in splitting up data and it's metadata into different locations. Instead, we settled on a looser coupling between structured and unstructured data, ie. saving references to documents in structured data and vice versa for the Alfresco Repo.
This implies that there is a way to reference the structured data, so a generic service layer must be constructed on top of structured data. An obvious choice would be a RESTful interface in order to integrate it in the Surf client layer. The content model can be used to impose constraints on references.
So, there will be no using repository services directly on structured data. Too bad, but the advantage is that the dependency between systems is greatly reduced.
best regards, Søren