I have to say I disagree, Your attitude is combative and points at flaws in (specific) design rather than the methodology (I’m intentionally ignoring the whole ‘right tool for the right job’ discussion).
A user state has nothing to do (directly) with a user component. A user state is required in multiple areas of the app, while the userDetailView merely shows a subsection of that state(and possibly formats it differently).
If your Redux state maps 1:1 to your components, you’re using the wrong tool for the job, it’s not Redux’s fault.
Like Redux, I also advocate that if you’re not sure if you need Redux, you don’t need Redux.
Regarding your whole singleton argument, that’s exactly how requireJS/commonJS works, so I fail to see your point. What does a singleton have to do with anything? (I’m exporting a singleton, non changing data structure, also known as a plain object)
Reducers in my opinion should handle all your business logic, your case is true if you don’t have business logic, but the UserDetailView is not a place to handle business logic, you won’t convince me otherwise.
All in all seems like you had quite a bitter experience with Redux, and it seems it’s mainly due to using it for the wrong job/task.
Yes, global state is code smell, but how unfortunate is that we need a global state for certain things — those certain things are what Redux was designed for.