This article provides a clear idea on whether React Router can and should be used as a replacement for React Hooks.

The Syncfusion Blog offers insights, tutorials, and updates on Syncfusion's suite of UI components and development tools for building modern web and mobile applications. Covering topics such as data visualization, UI design, and application development, the blog provides resources for developers looking to enhance their skills and productivity. Developers can learn how to leverage Syncfusion's components and libraries to create feature-rich and visually appealing applications that meet the needs of their users.

Syncfusion

Hookrouter was introduced as a flexible, fast router based on Hooks. Hookrouter produces the same outcome as the React Router but in a more streamlined and lightweight manner. We can apply the navigate() Hook to the direct URL of a particular page. The only difference is that instead of loading a new page, Hookter moves navigation to the history stack.

Will React Hooks Replace React Router?

IMO, No, it wont.
The examples are using the older version of RR (v5). With v6, the structure is both simpler and more powerful… and they have their own hooks.

It’s good, I’d love to see it becoming more common, or maybe even built into react itself

Most likely not! There’s a lot of consideration to be had for paradigms and packages, and the reality is, there is no hook-based routing paradigm that has the same level of backing and support as React Router.
This is like how you see discourse about SWC or other bundlers replacing WebPack- but no one of them has the same traction or community bulk, and as such, none of the same adoption rates, as WebPack.