Thank you for bringing this issue to our attention. After careful consideration, we are closing this issue.
This behavior is intended as the original name is the one set by default when "renaming" a profile. Then it's conflicting with an existing one (itself) and this is intended.
Thanks for the feedback on this, but after consideration we will keep the behavior of renaming this way.