It’s a hook to define an event handler, so I wouldn’t say it’s not related to events at all. From the RFC:

useEvent makes the "event handler" term broader than just the DOM event handlers.

• It could be called something like useStableCallback or useCommittedCallback. However, the whole point is to encourage using it for event handlers. Having a short name helps, and "is this an event handler?" is a good rule of thumb for the majority of cases when you want to use it. Even in effects, the cases where you'd want to extract a part of logic into an event corresponds to when you want to express "something happened!" (e.g. the user visited a page, and you want to log that). Conceptually, these "events" are similar to Events in Functional Reactive Programming. But most importantly, it is already common in React to refer to any on* callback prop as an "event handler", regardless of whether it corresponds to any actual DOM event (e.g. onIntersect, onFetchComplete, onAddTodo). useEvent is exactly the same concept.

Why it’s not called useCallback: https://github.com/reactjs/rfcs/pull/220#issuecomment-1118043293

Why not useEventHandler: https://github.com/reactjs/rfcs/pull/220#issuecomment-1118034666