If "top priority is grow users on the protocol" and the original naming strategy is "extremely confusing for new users", it feels like a swing and a miss to view developer feedback as more important than the advice you could get from people who regularly work on challenges such as: adoption, onboarding, retention, etc.
Creating a name that can scale, and a brand that is magnetic isn't some fluffy soft skill. It's work that deserve's to be taken seriously, and skipping that step causes ALL kinds of problems in the future (the problems that the developers are being asked to weigh in on, actually).