Azure Table Storage can store more No-SQL structures so is potentially more complicated than your average flat-file. Even different rows can have different schemas as per this example. Polybase on the other hand is optimised for highly-structured flat files and loading high volume at high speed. It has a fairly simple interface where you can set the file type, separators, a few failure options, but not much else. So in answer to your question, Table Storage data could potentially be more complicated than could be optimised for high speed loading via a simple interface like Polybase.
However this is not a problem as Azure Data Factory can import from Table Storage:

Polybase has recently been extended to support Azure Data Lake Store (ADLS). If you feel strongly about this, you could post a feedback request:
https://feedback.azure.com/forums/307516-sql-data-warehouse