preface: I've briefly looked at 4.7 on a development server, but haven't had a particularly intimate look-through yet. based on that and my being relatively new to drupal, advance apologies for any needless ingemination.
The features in question have to do with workflow when setting up content and modules, as well as default drupal blocks that aren't modularized (or are lumped into things like node.module). Namely things like "who's online", which we'll start with.
The non-module (or more accurately non-dedicated module) state of certain features seems confusing since:
a] the user then turns some things on in modules, and some explicitly in blocks.
b] there's no way to set access rights for non-modularized blocks such as "who's online"
(There've been similar posts regarding customization options of core components, namely a lack of any powerful customizability for things like the $links array, which I think'd do well to be untied from node.module and elsewhere, and placed in its own module for added extendability.)
I bring this up since it seems a bit odd I s'pose that things like authentication are modularized, but some simple 'who's online' function has no settings, no access control, nada.
Lastly, the current workflow on the backend requires a user to hop from one menu to another: enable module, save. adjust settings, save. adjust access control, save. enable and set region if it's a block, save. Having the focus of the backend be more "module-centric" would be a nice thing to see down the road. A hypothetical example of an improved workflow might be something such as: