Two departments or companies aren't going to use the same subset of C++.
Coding standards also evolve over time as languages evolve and better ideas about software engineering happen. 2015 C++ is much different than 2000 C++. Unless you always work on greenfield development with coworkers that strictly follow the same standards and C++ subset and you never do any kind of maintenance work, you will need to learn more parts of C++ than you may personally wish to use or learn.
I guess I just don't understand why people consider "too many features" to be a shortcoming.
Complexity and subtleties in a large language can make it difficult to write correct software.
I can point to one policy that guarantees safety becomes much easier: prefer modern C++14 idioms whenever possible.
That's a mighty large assumption.
Typical physicist--at least you can approximate many C++ developers as spheres!
If you aren't expected to do this, or even to be able to, perhaps the language is poorly designed.
But it was painful at times, and required a tech lead who could really enforce their opinion about what code should look like. In the end, at crunch, code was often written that used features outside the subset, and everybody did find themselves having to figure it out, to learn more about the language.
"Just use a subset" was always a solution better in theory than in practice for medium sized teams.
How big is the team of developers you have in C++, and what proportion have written code in other C++ shops, and how time-constrained is your development? C++ for R&D type projects is very different from C++ for getting a shed load of features out the door on time, in my experience.
In the case of C++, it's neither required, nor even possible to learn ALL of C++ (not without a couple decades of experience). C++ is a monster, a colossus, a many tentacled monstrosity of hundreds if not thousands of sometimes very complicated features. You cannot possibly master it all.
Yet the barrier to entry is as high as C, if nothing at least because C is a subset of C++. You don't have to be a template metaprogramming wizard and make full benefit of the latest standards' new features in order to know C++. As an example, in my work in physics I use C++ consisting of C, templates, the STL and POD structs. I don't use C++'s immense OOP tools simply because I don't like/don't need them. Someone else might use the full OOP features of the language. Still someone else might reduce it to C with templating because they like C but hate not having generic programming.
In short: C++ is what you make of it. Your C++ is a subset of the C++. It's your job to decide what features you want to learn and make use of. Don't feel like you don't understand C++ because you don't know Stroustroup cover-to-cover by heart.