All such queries would represent implementation-dependent features. I think the ANSI standard says the answer is NO.
In Access, the answer is NO because SQL queries tables but you want to query a TableDef, which is NOT a table in Access.
Now, there might still be a way - but you would have to write some module code to do it. If you wrote a function that could be given a parameter and return a table property, and if the function was declared public, you could use it in a query.
Unless you are using this for documentation, I see no need for such a query. You cannot do much with the table's definitional data in a query context. If you could get the data into a table or query, you still would not be able to do much with it. On the other hand, direct lookups in a module can make the data available in a context where you could actually use it.