'Gate' architecture and asserting query as defined

[alisasila]

Hey, I'm struggling a bit to find a good way to structure and use react-query for a specific part in my code.

I have 2 "gates" I want my app to go through before my screens and features get executed.

1. A gate that fetches data about a user, showing a loader while fetching, and then passing the user to a context. That way user will always be defined after I "pass" the gate.
2. A gate that fetches a healthy chunk of data based on the user that is already defined. Same thing about showing a loader until the data is fetched, but this time I can't (or don't want to) save it in a context because it is a fairly big chunk of data.

The question is how do I indicate to all the code that comes after passing gate 2, that the chunk of data I loaded there is actually defined?

I'm using V5 and know of Suspense, but my team lead prefers I don't use it (says it might be prone to leaks and that throwing Promises might be odd).

I could also assert it as defined, but if there's any other recommended method you might suggest I'd much prefer it.
If perhaps there are resources/examples you might conjure up that seem similar to the structure I'm looking for I'd also appreciate links.