The benefit is that I can use scoped CSS on any given article I write to better match its content. And writing in pug is, to me, equivalent to writing in Markdown.
I import in packages if/when I need them, instead of relying on a plugin ecosystem.
But this is not a CMS: it's me writing pug, compiling, and generating static pages.
If this were client-facing, I'd need to drop in a CMS/db. But since it's only me, this system has been ideal.
If you didn't need a CMS then I'm not sure why you were using Drupal/Wordpress in the first place. The only reason I can think to use them is if you want to hand off content editing to a non-developer.
But neither is my website a simple brochure site. Members create their own content, upload photos, enter their location on a map, enter available dates, have the ability to chat with other members. When I tried to do al this with custom and available plugins, it never felt as a coherent experience. Then there is a lot of automation in the background, notifying members of unanswered messages, expiring profiles, notifying members of expiring memberships. Getting all this properly done with the CMS provided API's is more work then writing it from scratch yourself. With the benefit of not having to worry about CMS API deprecation.
I was saying "client-editable content" vs "not" and you seem to be saying "brochure site" vs "dynamic site".
Brochure sites sometimes need to be client editable. And sometimes complex, dynamic sites don't. It's an orthogonal point.
I rewrote the site in Node.js/Express with Vue.js and server side rendering. The ecosystem is ready with so many libraries to quickly get up and running. Another major benefit is being able to design your own database instead of having everything stored as a post (WordPress).