So I actually figured out a solution. The meta function takes certain parameters, and one of them is matches, and inside this matches parameter lies all sorts of information coming from the routes, and of those data points comes from the main layout route, which in my case is where the loaderData logic lies, so that data is available inside the array of objects return from the matches param natively available from meta.

Thanks for looking at this @Drew Reese!