The simple answer is that there have not been many requests for this feature. This thread notwithstanding, look around and you'll see that we haven't been asked much in the 4 years SkyView has been for sale.
We maintain a huge list of feature requests, and do our best to prioritize them. It has nearly 1,000 features on it, so we have plenty to do. This feature is on that list, but it hasn't bubbled to the top, so we haven't gotten to it yet.
I think one of the reasons that it isn't asked for is that once you fly SkyView, you will see how good it is at giving you actual knowledge about the terrain all around you and along your flight path, not just in the few seconds before you hit a mountain. Our goal has always been to warn you far in advance of an issue. In those dark nights in the Arizona desert, I'd much rather see 100 miles out and know there is nothing in my way, rather than deal with the terror of an unexpected terrain alert. I hope we can all agree that it's better to never get within 30 seconds of a crash than to only warn once you do.
We do this with SynVis in SkyView, where everything above the line is a threat. More than that, our look-down map always highlights terrain that is an issue, no matter how far away (even in Europe when you are in the USA!). This way you can see that you are going to have an issue in 100 miles, not just when the little box in the corner pops up a few seconds before impact.
The thousands of users flying with SkyView find these methods very effective. They lead you to "just knowing" where the terrain is. I believe it is because this system is so effective that it means customers don't ask for an enhancement to this as a primary request. Look at the image below, and you can clearly see where you shouldn't go even though it is many miles away.
Now, with all that said, it is on our list, and we do expect to add it someday. But let's not act like it's easy. The last thing you want is a terrain warning going off all the time. It needs to filter itself out when it thinks you are landing. It needs to not go off when you do a loop and are on the downline at 200 MPH (only 17 seconds to impact at 5,000 AGL). It needs a way to cancel it when it is going off an annoying you. So it isn't just a few lines of code. There's a reason the TSO for TAWS is 50 pages long!
As a final note, CFIT is on a steady decline in the last 10 years, especially in well equipped homebuilts. GPS units seem to be doing their job. 15 years ago CFIT was the killer, but today it's loss of control (stall/spin and other bad piloting).