TimescaleDB distributed setup strategy
Current version of TimescaleDB, which is 2.0.0, doesn't support push down of aggregates to data nodes (see limitations) and all joins are performed on the access node. So for the queries, which join a distributed hypertable with non-timeseries data (which, I guess, are stored in normal tables), the data will be brought to the access node for the join. Thus you might want to store non-timeseries data on the access node. You can also manually distribute non-timeseries data, however there will be no performance benefits.
Note that if a hypertable refers to non-timeseries data through a foreign key, it is necessary to have the non-timeseries table on the access node and all data nodes and the timeseries data be partitioned across data nodes in the same way as the hypertable.