Yes, the new Litchi capability has been discussed in other threads. It is a nice addition. I like it. However, it does not really address all the concerns mentioned in the older posts above.
It's true that Litchi will now let us set waypoints with reference to ground elevations, AT the waypoints, but not along the path between waypoints. In terrain like the rolling hills of Virginia, it's sometimes very difficult to visually see the peak of the hill in the imagery in Mission Hub, and an elevation rise might be in the path between waypoints. So I always end up opening Google Earth so I can cursor through the entire mission path, to be sure my altitudes are sufficient to clear nearby elevation rises. Often I have to change the mission plan to set waypoints at those tops, just to be sure I clear them. Also the terrain elevation vagaries (trees, pond bottoms, etc) in Google Earth are still a problem with the new Litchi capability. Litchi doesn't have their own database; they rely on the same data in Google Earth to make their automatic conversions to AGL. Also, I still have to check for cultural obstructions like power lines, or towers or buildings. (Not so much a problem in the trivially easy terrain in the video above, but nearly always an issue in other areas, like the East coast, where we don't have those big sky views so much).
So even though I like the new Litchi capability, I find that I have to do almost the same work I had to do before it was introduced, particularly on long distance Litchi missions. The new Litchi feature still isn't a substitute for the KML file method using Google Earth above, because it doesn't consider the entire flight path, only waypoints. And I still have to at least manually cursor through Google Earth and double check calculated altitudes of everything in the flight path in Google Earth anyway.
But I'm not complaining, I like the new feature for other reasons. It certainly makes waypoint planning easier and more intuitive over relatively open terrain. It's easier to set altitudes above ground level for things like that, without having to do the math for conversion to home point reference altitude.