Really not sure where you are going here. What specifically is the "view boundry"? I don't see how single, multiple, or hierarchical views make any difference to model/view separation. What is the difference between a single template made of blocks where the view might have a method to deal with each block, or splitting the blocks into multiple files and having a distinct view object deal with each block. Same code, same separation, different orginazation.
Composite views use template fragments rather than a unified, whole page template but all formatting knowledge, I think, belongs on the other side of the view boundary. The application can present a set of data without knowing anything about how that will be used to build a page.