If your tables have very heterogeneous column names, like 1 column will identify any table on average. There will be some duplicates but the median columns will be one or two.
If your database has very homogenous column names you don't need to identify a single table for autocomplete to be very precise.
Sure you can do something that is close enough, but the LINQ authors were looking for precision in the autocompletion and for the LINQ query to have the same ordering as expression syntax.
The goals of this syntax are very precise and people seem to like it. Once again: calling it dumb is uncalled for.
It doesn't require a time machine, just a basic understanding of statistics or probability.
On the other hand, statistical autocomplete is not as good as having a precise autocomplete that does’t require jumping around lines.
My point here is that different people enjoy different things. There is no need to shit on other people’s accomplishments or preferences.
If you are right about why they did it its even dumber than my reason, they are changing a language grammar to let them make a much worse solution to the same problem.