This is a big question, but maybe these questions can help guide you to an answer that works well for you:
- How many pages is the website? If there are 20 pages and they follow the same design where only the page text changes, then you can likely reuse aspects of your design in Hype and lean on your CMS for content updates.
- It sounds like you're happy with how your menu + pages adapt on multiple resolutions. If you then begin slicing up your single .hype document into multiple pieces, this introduces additional complexity into your project that seem like they can be avoided by retaining a monolithic .hype document export. The caveat being: if this webpage takes a long time to load just the generated .js file containing all your symbols and text across your project, then splitting it up into individual pieces may make sense.
- We have definitely seen situations where Hype has been used as a mockup + playground for design, and then it becomes just as performant to use this Hype export as the production/deliverable file as it would be to recreate the design in traditional HTML/CSS. Making sure this site is updatable as well as performant for end users is important, so I recommend making sure you're taking advantage of a few performance tips and testing in your targeted browsers + devices.
I think the question for me is what does this website look like when you export straight out of Hype? How long does it take to load on an average internet speed your visitors will be accessing the site from? If you split up a Hype document into 4 pieces, this will actually load the whole site slower as more connections are required to download it all.