The only input I'm seeing here is "this is new and I don't know how to use it".
I don't think that's it. Then why remove dumpprivkey entirely? Why not update that CLI response to include the WIF and a descriptor of the path? Remember how long `getinfo` was deprecated before it was actually functionally removed? Not sure what the rush is...
I have seen people complaining about not being able to see their address(es) because they imported their key(s) into a wallet that only makes a specific type of address. I have seen people confused why when they import a xpub or xprv that the wallet generates a completely different set of addresses than they are expecting. Descriptor solve these problems by explicitly stating what kind of addresses to create and what the derivation paths are.
The confusion we all see on a regular basis is because of the backwards compatibility of output types, and because wallets are free to deviate from a standard (as they should be able to) -- to that end I think we just need to accept that confusion will always exist.
Creating yet another
new standard that may not be adopted by most wallets just creates an opportunity in the future for more confusion. Similar to how we saw wallets completely diverge on an HD standard.
I know the goal is to improve bitcoin, help others and make loss of funds more difficult but I think in a few years time we will have some users with descriptors and some without. Users asking how to recover funds without descriptors, or how to import if their wallet doesn't support descriptors.