My strategy when contemplating kni integration was more that Hype could be used as visual setup and the renderer of scenes (like a template), but would ultimately be driven by kni/the story environment. This would get around some of these current scaling issues. It sounds like this is the approach @kerguelen is also taking?
One of our goals was that you’d be able to label specific elements via class names or give certain scene names for particular environments, then glue code could associate the Hype template scenes with what to show and fill in any blanks.
Taking this further, the goal was to also make an Export Script that would glue them together.
(P.S. As a kid I was using HyperStudio (a HyperCard clone) making “escape from middle school” interactive fiction so there’s a soft spot for me personally, and those experiences did inform the design of Hype!)