For all of the above that were asking about the Sense reloading issue, apart from the many, many, many threads and posts here in the Android Central LTE Forum that mention it (just do a search for "sense loading," "sense reloading," "sense resetting," "sense restarting," "sense crashing" "sense booting/re-booting," and "sense ate the last piece of cheesecake....") here is a brief history:
In general Sense has had "reloading upon return to home" troubles across platforms for about a year or so depending on the device and the update where it seems to have started:
http://androidforums.com/evo-shift-s...ing-issue.html
http://androidforums.com/htc-one-x/5...-crashing.html
http://forum.ppcgeeks.com/htc-touch-...htc-sense.html
Sprint Community: HTC Sense Issue Consolidation Thread
http://forum.xda-developers.com/arch...t-1139314.html
HTC Forums
HTC's "community" forum had a number of threads about it which pop up if you do a google search but seem to have been deleted:
http://community.htc.com/na/msgs/def...px?MessageID=9
Specifically with the EVO LTE:
http://forum.xda-developers.com/show...php?p=26735055
http://forums.androidcentral.com/htc...9-loading.html
http://webcache.googleusercontent.co...ient=firefox-a
This is also a problem on the One X:
http://forum.xda-developers.com/arch...t-1601619.html
For me, I started having problems with it on my OG Evo a few months ago after having the thing for a year and a half with it not being a problem. Can't be certain, but would not surprise me if it started happening after a Dolphin Browser update. I note in some threads that going to Dolphin mini seemed to help some people and exiting out of Chrome seems to be one of the biggest triggers to the problem.
So what to take from all of this? Well, it is clearly a known problem that has been around for some time so don't expect an OTA to fix it anytime soon. It seems to stem from (surprise, surprise) how much of the RAM Sense takes up and how sense handles conflicts for scarce resources. Therefore, if you only use the stock browser, close out apps totally, keep your cache cleared and don't do any thing too demanding RAM-wise, you may never experience the issue.
If it is a problem, then the third-party launchers do seem to take care of it and, of course, there is rooting. The only reason I have not rooted yet is that I am a bit lazy and i want to make sure there is not some sort of huge OTA update that will cause the dev's to rework their ROM's and also to give time for people like Viper to get all the tweaks and mods in place.