Not making assumptions about “starting conditions” was a learned activity. These days, part of an .Initialize procedure’s job would be to put a database in the desired state - summaries removed, all records selected, fields sorted in the expected order, etc.
I can see the use of an empty database - as the container for the input of imported data - often it would be an intermediary - to pre-manipulate the data - between the raw data and its eventual home in another database.
In the (very) olden days you might get rid of that “shadow” record by importing, then select NotEmpty on a field that would always have imported data, and RemoveUnselected. Yes, very old school. Now I’d just import with Replace.
But what if you want to delete all the records - can’t do that until you add an extra record back in. You could select the added record on its field being empty, then RemoveUnselected and you are back at the start.
For added assurance - because I don’t like to rely on things being “empty” (A space looks a lot like “empty” on my screen), I’d probably put an unusual character in that “shadow” record field and select on then RemoveUnselected.
Or, if it wouldn’t get in the way of your selects and counts, you could just leave it in - not take it out after Import.