It's a stupid system, even without looking at it. I don't see it as having any advantages.
You have to deal with homophones. Their.bare.deer and There.bear.dear.
If it's universal, you have to deal with all interlanguage homophones, Si in Spanish, Sea, and see in english, ci in French.
Spoken language carries a lot of information by context. Try to transcribe random words. In normal language the context of the word before gives you information about what word to expect next. If you have ever had a radio conversation over a noisy channel, you find that a single idiom or allusion in your speech can side track the whole coversation. If you have ever had a conversation, not understood a phrase, then replayed in your head to use the words after to "reconstruct" what was said you will get an idea of what I'm talking about.
Written language has it's own pitfalls. Are you going to limit your system to ascii characaters only? Do other nations have to give up all their diacritical markings on letters? Do all asians know latin lettering?
The net result will be that you are going to have to spell it out phonetically, or send it as a text string to anyone who needs an accurate transcription.
I don't take my phone with me in the back country. There's no reception. How do I find out the code I'm in.
Like the phone system, it tries to avoid having neighbouring zones having similar coordinates (area code/words)
The conventional coordinate systems at least are tolerant of certain errors. Degrees to 4 or 5 decimal places locate you close enough to hit with a pine cone, and if you are going on a conventional outing, your base people know where you are to some fairly close degree. The whole idea of UTM is that 6 digits gets you to within a football field -- if the person at the other end knows where you are to within 100 km first.
How many of the rescue agencies use it now? So you have a delay while they turn Electric.Ambling.Hippos into a lat/long set of coordinates on some web page. This can be a serious delay, as the helicopter base station doesn't have cell reception either. And just hope that someone writing this down didn't put down Erection.Rambling.zippos which is over in East Horsebiscuit, South Dakota.
I used UTM grid once to report an accident. My GPS was set to that to work with the topo maps I was carrying. Those maps have a UTM grid but lat/long only on the edges. UTM is much more useful on the ground. Turns out the chopper pilot only could work with lat/long. That's what his device read. Cost me an extra 20 minutes wait, EVEN THOUGH HE HAD THE EXACT SAME PAPER MAP I DID. Didn't cause extra grief. Boy had a torn knee ligament.
I do have an InReach. Push the "HELP" button, and my coordinates are on their way to my designated contact. If you have a SPOT it works the same way. If you have a PLB, turn it on.
When I'm the back country, I set up a list of checkpoints. I leave a copy of my maps with the checkpoints with my contact in civilization. Daily I send back both the lat/long but also my text location relative to the nearest check point. (2 Km East checkpoint 6A) to give some degree of error checking if someone doesn't transcribe the coordinates correctly.
As a nav aid in what passes for civilization, I can use my phone to send a pin. If I phone 911, my location goes with that call.
As a game aid, make up your own.
I ran a ROGAINE style program for 6 years. I had 1300 controls scattered out over 200 km2 of territory, each with an alpha numeric ID and a code word. Clues had the ID, Finding the control with the same ID showed you found the right one. Returning the code word showed you'd actually been there.