I think this feature should be expanded to include locking field configuration as well as views.
I was just working with a user case for the locking functionality that cannot be solved by multiple users.
When practicing view configuration with a new user, the user has to be an editor/admin. However, it would be prudent to lock essential fields that are core to the data model and should never be edited/deleted.
I think this is core to the “Fear Management” @B_Sp mentions here: [DONE] Undelete Fields / In Audit Log, keep activity in Deleted fields
While it’s great to be able to recover information, at the end of the day, prevention is better than a cure.