Okay, I've had a chance to live with 3.0 for a while. Here are my impressions.
Most importantly to me, they've fixed the erratic topo contours of 2.0. Now the topo contours are consistently displayed, and the data seems to be high-resolution and accurate as far as I can tell. The downside is, unfortunately, that the contours are now nearly invisible on the dark green background used for park areas. I spend much of my hiking time in park areas, and while I totally appreciate a mapset that shows these land boundaries with a different color (vs Ibycus which uses color to show vegetation), it'd have been nice to use a ligher shade of green so the contours would still be readable.
The SATM trail data appears to have been removed, as requested. I checked a few trails that were present in 2.x and they're not there in 3.0. There are
a lot of trails still shown however, and I imagine these came from a different data source. Trails are shown with rather wide lines, and the whole display seems to be optimized for Nuvi-type units. (These screenshots are from my trusty old 60CSx. I skipped the installer, so if there's a Nuvi-vs-handheld option, I didn't see it. There wasn't one last time.)
I've noticed a bunch of new POIs, such as restaurants, bus stops, mountain names, campsites, and the like. Oddly the POI text is shown above and to the right of the POI symbol (see the two examples in the upper-right screenshot), but at least the info is there. I think the oilwell names and LSD boundaries are gone, though WMUs are still shown.
Auto-routing is still slow to useless. A route from my living room in Edmonton to a cache on an oil-lease road a few hours north takes about 10 minutes to calculate before returning an out-of-memory error. Another out-of-town destination took at least 5 minutes to calculate, but it did succeed. When I needed to go from A to B a few kilometers through residential areas on my bike in Edmonton, I set the unit for shortest route and bicycle, and it did come up with a good route fairly quickly - though it seems to think the residential streets in this area are "ramps"; while going east on a numbered residential street, the prompt said "north on ramp". Details...
But this is first and foremost a mapset for back roads, and it seems to do that well. I didn't compare the new version side-by-side with an older one, but in my limited checking from memory, road detail seems the same as before. Of course there will be some new roads; I just haven't stumbled across them. The new NW portion of Edmonton's ring road isn't there yet.
The lower-left screenshot shows an example of the backroad detail, a place where I parked at the top of the screen and followed cutlines to a cache at the shore of a pretty lake. Same detail here as version 1.0, and it helped a lot for this particular cache. (Who needs a boat?)
In short, 3.0 is an improvement on 2.x, but I still
prefer 1.0, and will be reverting to that shortly. (If you have any specific questions about 3.0, ask quickly before I make the switch back.) 1.0 has readable contours in all areas, has DEM shading and intermediate elevations (when the arrow is between contours), and it routes faster if not particularly better. And it's just more pleasing to the eye on the 60CSx. What 1.0 doesn't have is high-res trails, but I can add those with a SATM layer direct from the source.