Plenty of those concerns go beyond Redux actually. But I can see your point. The challenge of React is connecting the dots and seeing how it all goes together. This gives you flexibility, but it can also feel overwhelming as technology keeps stacking up and solutions come and go.
That said, you can build the complexity as you need. I see Redux more as a guideline. It pushes your state management to a certain direction and favors certain style of programming. The data flow if explicit. Even though there is boilerplate, once you acknowledge it, you can code plenty of that away. Instead of verbose data queries, you'll end up with something more terse and so on.
As time goes by I expect we'll see more opinionated options that build on Redux and all that. create-react-app mentioned by @jiyinyiyong is a definite step towards this direction.
Even though the community has gravitated around Redux, it's not the only option. This is both the blessing and curse of React. You'll need to choose your tools so that they fit the problem at hand rather than following dogma and kludging your problem to work with arbitrary tools.
All of these solutions have their sweet spots and it also depends on your experience making it even harder to choose. It doesn't help the landscape keeps changing quite fast as new approaches are discovered. I expect we'll end up with more stable solutions as enough time goes by and React ecosystem matures.