Let's collect a list of information we don't expose yet, but might be helpful to build a partially decoupled admin UI:
- A list of all permissions #2947605: Add a user permissions resourceLink
- A list of modules (enabled and disabled ones): Link
- Changing passwords: #2904451: Allow to change password through RPC endpoints through the reset password workflow
- Menu links: #2732283: Menus: ability to retrieve all menu links for a given menu, regardless of whether a menu link is defined in content/config/code / Menu Tree: https://github.com/jsdrupal/drupal-admin-ui/pull/23
- Code-based, not config-based provisioning of REST resources: #2822201: Allow contrib modules to deploy REST resources by creating routes, removing the need for config entities in that special case
- Conveying which fields can be edited: #2665602: Implement an API for REST clients to know which fields are editable
- #2919182: Web service to download private:// files
- #2771353: Support "auto-create" entity references by value (instead of by ID/UUID), just like tags are auto-created in the content creation UI
- #1869338: Support ETag + If-Match for PATCH requests to prevent concurrent updates
- #1916302: RFC 7807: "Problem Details for HTTP APIs"— serve REST error responses as application/problem+json
- #2947759: Simple configuration REST support
- State API - This would let you put a site in maintenance mode
- UserData - This is what stores whether the user contact form is enabled or not
- Cache rebuild