It’s the same reasoning as with deletion.
We treat the content explorer as a read-only interface by design. Even somewhat safe actions like renaming can introduce issues, such as breaking assigned system, or core, and potentially causing confusion if done accidentally.
Keeping the explorer essentially read-only ensures the same experience where content can be safely browsed and launched without the risk of unintended changes. Anything to do with management tasks like deleting, renaming, moving etc., are best handled externally, where users have full control and a better view of what they are doing.