Hi! Yes, it's certainly feasible.
Take a look at the old apostrophe-localization module (for 0.5):
That module works by adding middleware and extending various methods deep in 0.5's model layer. We would follow the same general idea, but patching the 2.x model rather than the 0.5 one.
That can probably be achieved best by writing a module that uses the "improve" feature to enhance apostrophe-docs, in the same way that apostrophe-pieces-import uses "improve" to enhance apostrophe-pieces. This should guarantee your extensions of the insert and update methods are called early enough.
You would probably also want to extend apostrophe-cursor, in order to ensure that the content for the current locale gets "swapped into" the properties where vanilla Apostrophe code expects to see it at read time.
Certainly this would take some doing. You could pursue it yourself, or you could arrange for us to do it via Apostrophe Enterprise Support, perhaps in coalition with other interested parties:
Will we do it on our own? Eventually, if our clients need it. But we've had few clients who required it so far; it took quite a while for a client to prioritize this for us with 0.5.
Let me know your thoughts!