In this case, I have some good news then. The way the hashes are generated, they are unique to any connection, model, sql, persistence combination (caveat, if the code used to generate derived tables changes, this may cause one-time shifts).
This means if your derived tables are stable and these parameters aren’t changing then the naming will be stable enough to query. You will still need to map from these more complex table names to their colloquial use, but they should be consistent over time. Hopefully this clarifies the situation, but I know product is looking at possible solutions as well.