The most important thing is cost-benefit analysis in this scenario, both economically as well as user-oriented. It isn't worth it even if there are some 'useful' scenarios. You're not getting a lot from it with the price you'd have to pay.
Proof of this statement? I assure you Apple has one of the most advanced teams and labs that experiments with myriads of design and technology implementations. Their ability to rapidly prototype is rarely matched in the product world. The process of design never has a consistent cadence when you take it seriously.
Sometimes there is no use for a cost-benefit analysis. As our now dead great leader once said, "people want a faster horse, not a car." You cannot bring new things to market by doing a cost-benefit analysis; the analysis will never work out. The iPad would never have survived a CBA. The iPhone never would have survived it either. Unibody aluminum enclosures wouldn't make the cut either. Making your own chips. Making our own OS. Making your own phone. None of those would survive a real cost-benefit analysis.
From everything I've read their design team is 12-15 people big. A team like that has been shown to suffer from groupthink by multiple studies, and that make for fascinating reading for anyone who wants to understand how teams work. Your blind faith in Apple's design process, if shared by Apple, shows the trap that designers and teams can fall into. There are things you can determine a priori, and there are some things you can only discover when you release it into the wild.