You really aren't asking for the autopilot to do this, you are asking for the map to do so.
Autopilots follow external commands. Go left, go right, go up, go down. You don't tell the autopilot to take you from KDVT to KCGZ, you tell the map to, and then you tell the AP to follow the map's output.
So, this is a feature you are asking for in the map. The upside to this is that it would show you terrain conflicts even if you didn't have an autopilot in the plane at all and were just hand flying a flight plan.
The downside is that this is exceedingly complex. The system can't assume that it can climb at any point since it has no authority over the throttle, and even if it did, it would need to know the climb performance of the aircraft at your current mixture. So, all it can really do for sure is turn at your current altitude.
How far before the terrain does it turn?
Does it take you all the way up a box canyon before deciding to turn around at the last possible moment, or does it just refuse to enter even if you are currently climbing, but might not make it if the user backs off the throttle?
When you plan a flight on the ground, how does it know what altitudes you will be at as you are at various points along your flight? Because it needs to scream at you before you depart that your route is going to be 2,700 NM long at your altitude, not the 120NM you think it will be.
Does it need to avoid airspace for you as it takes you somewhere you didn't ask? What about weather?
How do you tell it the attitude is OK if the computer has an issue and is blocking you from going where you want?
What if your new route leaves you with zero fuel long before your final destination?
And probably a hundred other things. At some point, there is a reason the pilot is in the plane.
At the same time, with the pace of avionics, I can't disagree that in 20 years, pilots won't be needed. Dynon has only been selling products for 10 years and look where we are!