Pro doesn't correctly load Excel tables if they don't contain any number fields. It treats the header row as a data record, as described below. This means I have to insert fake data into my Excel files or import them into a geodatabase, or some other workaround. Since I am often the only GIS user on projects that share a lot of Excel files, this is very inefficient, and simply frustrating.
"For tables that have all text column data types or have null values in the first row, column headers will be autogenerated (for example, Field1, Field2) when the table is opened."
Why is working with tables still such a headache? Esri customers have been asking for better table tools for decades.