What is the maximum number of columns allowed in a TimescaleDB table?

Do hypertables in TimescaleDB share Postgres's ~1600 column limit? I am writing a system to store a large number (1000s) of sensor values into a table, with one nullable column per sensor value. Since the table storage is columnar, I don't expect a wide table to be too bad for performance because each column is stored to disk separately. However, I will run into the column size limit if one exists. If I can't use a schema with a very wide table, I will probably denormalize into one table per sensor, with a single value column. Would TimescaleDB be likely to offer significant improvements over Postgres for this schema (many tables with a timestamp and a value column)?