I'm -1 on making this a global change.
I'm concerned about how you would do generic methods without BaseClass. E.g.:
doSomethingBasedOnRecordType( BaseObject rec )
<use introspection to determine action>
Yes, I guess you can do the same thing using an object type. But IMHO, having at least an Interface to limit objects to valid records is better for documentation and compile time error checking.
FWIW - I have a bunch of code that does just this. Some of it does generic stuff with the assumption of the presence of BaseObject methods in any record.
IMHO, while this is a nice way to migrate, it would add require too much existing code to be changed if we just dropped BaseObject all together.
Having an interface seems like better middle ground.
If integration with external frameworks is a requirement for a subset of Torque users, then perhaps this could be an generation time option.
Also, don't we handle a lot of this with the Beans generation options? If you need to interface with another framework that deals with POJO objects, just create a bean and pass it around. If the remote framework requires annotations, perhaps this is where that should happen.