A nice hit, thank you for sharing this these ideas.

When comparing WordPress with Drupal, you will see WP is outperforming Drupal in its easy content creation in posts & pages. I mean a very powerful editor integrated with media library, and a lot of hidden capabilities of its editor (internal linking, spell & grammar checking, embed support, mark down support, etc.). You will really miss them when using Drupal 7 and even Drupal 8. In Drupal you should install and configure a lot of modules (plugins) to prepare an editor friendly environment, so they are planning to enhance their Author Experience (e.g. media initiative).

BUT ...

When it comes to more complex use cases (e.g. universities, ... , web applications = big clients), you will front a lot of shortcomings of WP core and should install and configure a lot of plugins, write a lot of PHP code, or find a developer to solve your problem. I thinks here is the pain point of content management in WP. Drupal is doing this very good, using modules like:
* CCK (to define fields and custom post types (CPT) in dashboard, no PHP coding. in core since Drupal 7 = Jan. 2011)
* Views (to define presentation of post types + other lists based on CPTs, relationship between CPTs, arguments, ..., to feed content area, blocks (widgets), RSS, etc. It's a real beast. in core since Drupal 8)
* Panels / Display Suite (allows you to take full control over how your content is displayed using a drag and drop interface. Arrange your nodes, views, comments, user data etc.)
* Rules (to define conditionally executed actions based on occurring event = configure workflows = Beast No. 2)

For a detailed review, see this post (Why Drupal Developers Make x10 More than WordPress Developers, Nov. 2013)

So I think page builders are hardly part of the solution.

I think Toolset components (the same guys behind WPML) present good alternatives of Drupal to WP. Although there is no alternative for Drupal Rules yet, and Toolset views is not as mature as Drupal views, but they are addressing the real pain points of WP.