Servo range for multicopters

I am following closely this project and the awsome work you guys are doing.

Today I was looking at the protocol stacks thread and FDR mentionned at some point using channel range (servo throw) over 100% for his ladybird with the stock walkera firmware and that he wasn't able to set them over 100% (at this point in time) with Deviation. I think, if I understood well reading the thread, that the current main tendency is to keep the servo ranges no more than 100% in order to avoid damaging the actual servos. While this is plain good sense thinking that could actually handicap multicopter flyers for "stunt" and 3D flying.

If we keep the ladybird exemple, you need to set throw over 100% for pitch, ailerons and possibly rudder in order to have good fun with the bird. Since there is actually no servos on these machines it does not present any hardware hazard to set the servo travel over 100%. I think limiting throw to 100% on these flyers will render them dull to fly under Deviation.

So my first question is: Do all the assumptions I made so far correct? If yes my second queston is: Would it be possible to create an "aircraft" type, like "Airplane" and "Helicopter", such as "Multicopter" (or whatever) and allow servo ranges up to 150% (or more) for that particular aircraft type, and only for that type of aircraft? That would keep the throw inside a safe range for the other types of aircrafts by preserving hardware integrity and protect against user input errors for planes and helis (and everything with actual servos)while allowing extended throw range only for the multicopters.