"Bloat" doesn't require that the features are literally useless, merely that their usefulness doesn't justify their added complexity.
And for many people, a huge portion of C++ falls into this category.
Just look at the 18 different methods of initialization for an example of this. Or look at ranges, which seem to simultaneously be far more verbose than the alternatives in every other language, while having measurable negative impacts on compile times (that have spread throughout the stdlib, so even if you don't use them you have to pay for them). Ranges are certainly "useful" but the cost/benefit ratio is questionable.
There are new initialization modes that are simpler. The old ones still have to work. But you don't have to use the old ones anymore.
Yes, you can limit yourself to the C and Java subset, just as you can drive everywhere in first gear, can eat all your food raw, can crap in a hole. Just because you can does not make it a good idea. Objectively, the more your code looks like C, the worse it is, because you are inviting into it all of the flaws endemic to C code.