That's fine, if that is what you want, but note that that has nothing at all to do with the layout in a single article - it only determines the layout of multiple articles when listed together on the page in the "blog/category" format.
Well, kinda! But now from reading your post, I'm wondering - did you create the first "page" by using multiple articles and having the "blog/category" page format create the layout for you (building what looks like a complete article out of several articles)?
If so, that is not the correct way to do that - you will end up with different "articles" that only combine into a single "page" when assembled with the "blog/category" format. Think about it for a minute, and I think you will see what I mean.. Do you really want to have an article that is only the "Amenities" section of a given property? How will you keep it clear that the article belongs with a certain property? I suppose, to a degree, the "category" can accomplish this, but that is counterintuitive and as your site grows, this is likely to become an organizational disaster. It also renders useless the idea of managing the site as a collection of articles than can be moved, reassigned, reclassified, recategorized, etc as needed when the contents change.
It is better to create each property as a single article, and in that case, yes - putting a two column table beneath the intro text (not an article, but just text as a part of the overall article) is a much better way to do it, IMHO .. and I think you should do that with the first article also (If you did it using multiple articles). You can certainly have the pages look the same, if you structure them the same way.
The "front" page complicates matters to some degree as it has it's own set of parameters in addition to the article parameters, and they are unique to that "front" page.
Does that make any more sense?