Does anyone here have practical experience using DBI's DbTypeSubclass functionality?

Tim Bunce added it two years ago, but it remains undocumented and sparsely referenced. (Big shoutout to princepawn for keeping the torch lit; SuperSearch shows this node is the only mention of the feature in the monastery archives.)

I'm in the process of updating my DBIx::SQLEngine distribution, which currently uses DBIx::AnyDBD to do dynamic subclassing, loading a different Perl class depending on which type of database you connect to. (For what it's worth, I think this kind of dynamic subclassing is a great solution to the challenges of creating cross-DBMS portable applications.)

In practical terms, DBIx::AnyDBD has been working fine... But, I can't help but suspect that there could be performance and other benefits that might be worth the transition to using DBI's DbTypeSubclass instead.

Anyone have any DBI dynamic-subclassing wisdom they'd like to share, before I dive in and give it a try?