<div>'s anyone???), and the hacky workflow to maintain an exemplar site for easy duplication into new projects, it's a no-brainer for design/wireframing/prototyping/etc., IMO.
I do know of Light CMS and Duda, but I haven't given them much thought since they are all-in-one platforms and as you pointed out, costly. In my experience, all-in-one platforms are typically (1) overpriced and (2) not as feature rich as you can get with a solution segregating design, coding and CMS, relying on products that excel at each.
Webhook is still my current CMS platform of choice (but I have also integrated into my agency's legacy CMS.) But I'm sure you are right -- it may seem complicated to some since Webhook's roots are in command-line tools (FYI - they do have a desktop-based app that hides all of that now.)
Fingers-crossed for the Webflow team regarding "cracking the nut" for integrating a CMS with their awesome design product. From what I read, it's been on the roadmap for a while, so who knows where that stands. Now, If it were up to me, I'd laser focus on the primary design product -- putting more engineering effort into widgets, better developer support and open-sourcing the core aspects of the platform, especially the export side. For example, if there was an API for the export process, then anyone could work on writing adapters to pipe/stream the Webflow output to anything.