From a usage perspective I don't agree. Reason being the record scripts will start giving you hard coded values in the script and it would be a huge mess when we have too many scripts. Also QTP at times uses more properties to recognize the object then required, this will make the statements more length and unreadable.
If it was possible to adopt recording or transformation to framework code then it may work.
I was thinking of it as being a separate recording mode such as low level or analog. I wouldn't always want it to be turned on. There could be controls for deciding what code it adds to the script while recording.
The real problem here is QTP has not moved forword in usability since I first used it many years ago. They have made changes sure however the same basic methodology still exists.
This age old methodolgy is flawed and unproductive. Writing or recording 1000's of lines of code for automation isn't really needed anymore, the problem is most automation specialists just don't want or know how to move on from the old ways.
I haven't used DP for years I did in the early days but there are better ways to do things.
5th Generation scriptless frameworks are the way to go. The issue here is acceptance by the automation community.
Recording in any form is just plain lazy and poor process.