I think the one case for Redux missed is when you need to share the same data/state across disparate components that may be in differing routes or different sections of a screen(overlaps with prop drilling).
For example, I have common subheaders in different screens on an app I am working on. The routes are different, but that component is sharing state across the different routes and parent components.