So technically IF you use the EQL AST and preseve the :component entry (make sure there is a :component on the metadata that has the correct ident function), then it should be fine as long as the ident function on the component is the same.

I think there are helpers: https://github.com/edn-query-language/eql/blob/main/src/edn_query_language/core.cljc#L369

and merge-queries

The problem that you are then going to run into is that the load itself wants a component, not a query; however, you can work around that one by making your own load function wrapper that just triggers the internal load mutation.

If you look at the implementation of df/load!, you’ll see that it extracts the query from the component. I used to have a load-data that would allow for an arbitrary query, but since the normalization logic on that wasn’t very clear I decided that this kind of advanced usage would be better to just let you do via direct use of the internal-load! mutation.

(transact! this [(df/internal-load! 
  {:source-key :person/all
   :query (comp/get-query Person)
   :remote :remote})])

Thanks. I'll try that out!

Keep us posted!