At least for Matter, I’d like to see the device profile be a dynamically generated construct that is created at the time of device commissioning. If that could be done, it might not require any changes to the mobile app which I think is always an obstacle to getting certain platform changes implemented.
One other thing that should not be overlooked is that an additional function of fingerprints is to identify which driver should be selected even before the device profile is identified (since the fingerprints.yml file that maps fingerprint to device profile is associated with the driver). Revamping that would likely be a much larger undertaking that could require fundamental changes to the onboarding process.
It’s a shame that when the Edge architecture was being created that there wasn’t a shift from doing device drivers that get loaded onto the hub and instead doing capability drivers that get loaded onto the hub. Then a device could be associated with the capability drivers for the capabilities identified during onboarding. It would have offered a more dynamic and modular approach rather than what we have now.