It sounds like you want to re-invent the wheel for your hovercraft.
You can do MVC in Moodle today. We have views, but we call them renderers.
And you should already be structuring your code around classes (models) to do all the real work. Until now you would typically have defined the classes in locallib.php, but in 2.6 you will use class auto-loading and put them in the classes folder in your plugin.
That just leaves the controllers, which in the Moodle world would be the scripts like view.php. That script should process the incoming data, make the appropriate calls to instantiate and possibly update the relevant model classes, and then call an appropriate renderer method (view) to generate the output.
The student-visible parts of the quiz already do a reasonably good job of following this pattern.
So, to use MVC in Moodle, you don't need some hypothetical future framework. You just need to write code that does not suck today.