I think we can agree that C++ is a complex language. That was kind of the point, maybe languages could be simpler and force the programmer to follow more strict rules, in a good way. In fact I don't quite understand why C++ is so complex, what was the reason for that? Maybe backwards compatibility with C, but then why C was/is that complex? Was it because that's how they were thinking about languages back in 1960's and 70's when most of them were invented, who knows.
C really isn't as complicated as people say, you just need to be a little patient with it and think through what you're actually trying to achieve. Yes, you don't have namespaces or structs with associated functions and private variables (object classes), there is no built-in boolean type (and stdbool sometimes conflicts with old libraries), and strings/char */char[] are awkward, but it's not that difficult to work around these limitations, or understand why the languages works the way it does. Not to mention, these very limitations can give you a different perspective on how you design your code, and push you towards alternative approaches like object pools and relational databases, both of which come with the benefit of knowing exactly where your memory lives, where leaks could occur, and how everything can be coupled, decoupled, or associated. It's especially simple by comparison to C++, for better and worse.
C backwards compatibility for C++ definitely adds to C++'s complexity. But it doesn't help that the C++ community is divided between OO patterns + 'RAII, not raw', and 'Stop abusing OO'. On one hand, there's a crowd that effectively wants Java/C# but with RAII pointers and manual/no garbage collection (C++ has been on this path for a while, D was almost there, but backed out, and Rust seems to be heading this direction), and on the other hand, there's a crowd that wants C, but cleaner and with some of the tools from C++ (which is the current mob voicing their concerns over C++'s future, and resulting in languages like Jai, and Unity's Burst Compiler). As a result, C++ is stuck in the middle, trying to cater to both, satisfying neither, and has become a kitchen sink full of dirty dishes. You'll find whatever you need in there, but you'll have to sift through the slime and clean it first.
Another way to make languages easier to use would be a higher level thingy created on top of an existing language. Some languages compile to C (or whatever), but I was thinking more like a "construction kit" for some language. For example it would be really nice to have a graphical design tool for planning class hierarchy in C++. It would make the first phase of modular (as in what file contains certain classes) design and also class hierarchy design much easier. I guess those kind of tools exist, but not in freeware/open source.
Isn't that what parser generators (i.e. YACC, ANTLR, Yeti, etc.) and compiler toolchains (i.e. LLVM, GCC, etc.) are for? Or are you talking about visual programming languages, or visual programming languages specifically designed for building scripting languages?
As far as I'm aware, Visual Studio does have a graphical C++ class designer. I know they definitely exist for C# and Java (and in all honesty, they're quite finnicky and not as useful as just hammering in code yourself, which is a shame).
As an added, you've probably already seen it, but Bob Nystrom is currently working on a book about creating scripting languages. It might be worth checking out if you haven't already:
https://craftinginterpreters.com/