I appreciate your reply. Map upgrades are not a big problem for me. I do not travel many places that are constantly in flux. I am amazed and disappointed, though, that with all of the USB inputs (A and C) as well as for SD cards and even bluetooth, that the engineers that designed this system would supply no  path to the RAM. Two programmers locked in a closet with a large pizza and a couple of Pepsis could have added that ability.
		
		
	 
if you take the usb "inputs" out you'll find it's USB-A and C interfaces on surface, but the "media hub" still runs on USB-B to connect to the headunit.
therefore, even with the onboard USB-C interface, charging speed is slower than your normal USB 3.2 dongles or the PCIe cards found on PCs. It is like running a USB-A to C adapter, you'll only be able to plug things in and read and write (to update OS or map), but not get 100% of the bandwidth for things that require more data processing.
Which is completely understandable, because why mess with something that works already and add features that 99% of the people won't use? 
Also completely understandable that not everyone is as tech savvy, so when/ if more customization is allowed, someone WILL F something up. The best course of action, for the OE developers, is to design something that is simple and user friendly with great UI, especially with the budget, resources, and timetable given. Think of it as developing a game. It is always faster and easier to develop a game with set variables than an "open world" game, that's why it takes forever for GTA6 to come out or it takes so long for Battlefield to release Battlefield 6 (destroyable world) versus Call of Duty's annual release - more customization/ user initiated changes/ freedom, more coding, more bugs, more things to go wrong vs creating a "box" and set specific "rules" (or physics, in game terms) and let players/ users play within the ruleset.
Another one is the OS... not sure what kind of OS core system it is, but it is definitely not opensourced or consumer-tier android based like those aftermarket ones are. That goes to all OE head unit development. Everyone locks their system, especially in today's world where almost EVERYTHING is CANBUS connected and can/ are controlled via the head unit. It is not only a copyright/ brand specific issue, but also a safety issue as well.
i guess what i'm trying to say is, it's not as simple and easy as telling the programmers to code in user programmable route information. there are lots of constraints in vehicular design and operating systems than what's on the surface. Being in the aftermarket industry myself, in both manufacturing and installation/ repair side of things, I used to think "how hard can it be?" until I realize how stupid people can be and how complicate things will lead to issues later (that's why I ALWAYS have to write the product descriptions and such in detail and include "please verify your vehicle's year, model and trim before purchase. if you are not sure please call us for verification. purchaser will be responsible for return shipping and restocking fee due to purchase without verification" you'd think people know to check their year, model and trim before purchase...)