[v6] useRouteState hook?

[forivall]

It looks like, in v6, the only way to access the route state is via useLocation -- and, of course, useLocation mentions

Note: If you're using this it may mean you're doing some of your own
"routing" in your app, and we'd like to know what your use case is. We may
be able to provide something higher-level to better suit your needs.

So, i wrote this quick abstraction over useLocation to better manage state of a route:

type RouteStateReturn<S> = [S | null, React.Dispatch<S>];
export function useRouteState<S extends object>(): RouteStateReturn<S> {
  const location = useLocation() as Location<S | null>;
  const navigate = useNavigate();
  const setRouteState = React.useCallback<React.Dispatch<S>>(
    (newState) => navigate(location, { replace: true, state: newState }),
    [location, navigate]
  );
  return [location.state, setRouteState];
}

My use case is to share a small bit of state among disparate components specific to a location, without having to clutter something like a redux store's state.

Are there any pitfalls to this approach? It seems to work fine. Could this be an addition to the library itself? Or as a recipe.