I wasn't accusing you, I was telling you what it is. (Look, we can quibble over what defines bandwidth theft, but embedding external sites in frames falls under a couple sub0sets of it, and it's just a bad idea in general).
Now including your OWN posts in your own posts is ... weird :)
http://wordpress.org/extend/plugins/embed-posts/ is an example of a plugin that can do it.
I think my "PC Review" example describes it best. You don't want a separate website for every subject (Drives, Monitors, Video Cards, etc). You want all of those items in the same site. And the ability to POST a review and discuss individual new items (instead of one comment field for twenty different video cards going back months or years.)
So you want a 'Drives' page that embeds the latest data from drives, with those comments, and you can update it whenever you have a new latest?
There really isn't a great way around that, as you've noted, because if you embed the content, you'll get the comments for the page upon which you embedded (i.e. if Drives is the page you send people to and Drives-1999 is the data, your comments will be on Drives).
So your proposed workaround is to embed, and I can see why you think it's logical. Everyone always goes to domain.com/drives, and the content and comments magically update when there's something new.
But ... that's just a strange way to go about it, when you could use categories or custom post-types (or Multisite, though I think that's totally overkill). And sadly even if you did embed, you run the risk of buggering WP because of the nesting (I imagine it would slow your site down).
If you forced me to do it, I'd use Custom Post-Types, call 'em drives, and make sure archiving is on. Then in my archive page, I'd pull the latest and greatest post as what shows up, and have a link for 'Comments' which sends them to the sub-page for comments (because having comments on archive pages messes with pagination). Then when I make a new post, the 'archive' page for drives (aka domain.com/drives/) is always the latest.
Thus you're using WP as intended, pages/posts as intended, and you don't have to reinvent the wheel.