The profile may not be the problem, it uses the “lock” capability and the driver can specify the source of the operation (see the “data” associated to the lock attribute in the capability, it supports a few reasons like manual, keypad, auto, face, rfid, etc.). So, the information is there and the SmartThings platform knows.
But you’re right and it’s not available for the user because SmartThings didn’t create a user interface for that. Just like happens with the brightness transition time for lights or the relative volume for Sonos, the production capability supports it but they never made the user interface for those features. In fact, you can’t even create custom capabilities with multiple arguments in one action, only the first argument will appear in the presentation.
Regarding the “new-matter-lock” driver, I guess the point is eventually making it the main one, otherwise it would not be called “new” but something more meaningful or feature-specific. Indeed, it’s hardcoded to only support a couple Aqara locks and one from VDE.