This is a title
Yes scraping pages can be very testing at times, but I think you've missed an obvious point in your lust for SDDX;
Some people don't want their pages to be scraped!
Do you really think Google wants you to scrape their search results, thus depriving them of advertising revenue and user profiles? I don't, so why would anyone in this position even contemplate changing the way they do things.
Let me put it another way. You run a blog/site (I assume you do), which generates a RSS Feed with full article content (as opposed to just a summary). How happy are you going to be when some T*sser uses _your_ feed to serve that content on their own page?? What if they serve it with ads? Suddenly, they are making money off your work, and giving nothing back.
That's why a lot of people will never switch away from something similar to the current technologies.
<rant>
Rendering on the client,
This is something of a bugbear of mine. You want me to view your content (otherwise you wouldn't have published), why should all the processing be done at my end? If it can be run serverside, you should take responsibility for the code and run it on your hardware.
People who insist on Javascript for a webform submission that could be processed by a serverside really annoy me.
Granted this is less of an issue with simple rendering, but it's still a risk.
How many businesses would ask their customers to take a risk that could be handled within the business. If Argos asked you to do it, would you not be a bit p*ssed off at their level of customer service? So why do it to those visiting your website(s)???
</rant>