No, not at all, you can name it exactly as you please, and rename it endlessly that doesn’t matter. What matters is the guid. So if an author wants to rename and by accident makes a new node coping the content from the old node, then everything is broken. Nothing can be done in those cases.
If it is only renaming the custom node, then you might need to “refresh” the node, that can be done by right-click “Edit Custom Node Properties”, press ok and the node should be “updated”
I have renamed my custom nodes dozens of times, no one has complained about that.
Zero-touch is a completely other ball game. Here is everything serialized into the dynamic library that is being loaded, which means that renaming is becoming something very different.
I am currently working on an update where I split my nodes into those that are Revit dependent and those there are not. This is to support the normal Dynamo and the standalone Dynamo versions. This will come with a price since I have to make two different superior namespaces (Orchid -> OrchidRevit and OrchidCore).
Said in another way, I have to choose if I will let the users put in new nodes so they are correct, or I will help them by setting up the migration but then remaining them as incorrect. Hard choice :-S