Visual object/collection naming convention idea

I'm not sure why this hasn't been implemented yet, after all these years, but if we want to name our objects how we want, and store them in distinct collections without seeing the .00x sufix. All objects can contain two variables that help with this problem.

string VisualName, and string InternalName

The logic behind it is simple. Blender can still do the auto-naming thing on InternalName variable, and the user can still see the chosen name in the outliner, which is the VisualName variable, cause blender reads the InternalName variable of every object.

For example:

3 objects with the same visual name. First one is named "cube" internally. And visually it is called Cube Second is named cube.001. And visually it's also called Cube And Third is named cube.002. And it's called Cube aswell.

3 Cube objects that are differently shaped, and have the .00x sufix internally, helping the user maintain the outliner organized, without needing to make a very tedious naming convention.

A system like this can work on collections aswell. Making them actually work like folders on the naming of the object inside them.

There would probably still be some limitations if the objects would need to be used outside blender. But other than that, this kind of organization workflow would get rid of having to make super long names.

The purpose of this idea is to get rid of the problem when users make lots of modular models and they're forced to add extra words in every object/collection just so they don't have the annoying suffix

Like, for example, these organized collections

Walls -> Metal -> One End -> Two Ends -> Three Ends -> Four Ends

-> Rock -> One End -> Two Ends -> Three Ends -> Four Ends

And so on.

You can keep the same names on the collections and objects if the user wants or has to, and blender only reads and changes the InternalName variable