I think for the US, they should ensure tzdata contains at least one city for every state. That’s what they do for Australia. Now, it so happens their current rules-only add city if in recent decades it had distinct time zone rules-happen to produce that outcome for Australia, because in Australia time is a state issue and historically every state decided for itself whether to have daylight savings and when to begin/end it. Still, I think they should amend their rules to say “capital and/or largest city for every first-level subdivision of major countries”, given some reasonably objective definition of “major” (e.g. G20 nations)

The problem in the US is that time zone boundaries very frequently do not match state boundaries.

It’s common for major cities to be located on rivers that are state boundaries, the area around the city uses the same timezone, and one of the states has a timezone boundary in the middle. Indiana has many tz database entries because of this kind of thing.

There are other fun cases like the Navajo Nation in Arizona.

Australia has an entry for a major city per state not because someone decided it was a good idea, but for the same reason Boise got one - they were the largest city in a jurisdiction that sometime after 1970 changed its timezone so it didn't match anyone else which necessitated adding an entry in order to record the unique timezone rules for them.

For instance, both Sydney and Melbourne both have entries because Victoria and New South Wales have started/ended daylight savings time in various years since 1970 on different dates like in 1990 when in Victoria it ended on March 18 while in New South Wales it ended on March 4.

It's also why Broken Hill has an entry despite being in New South Wales, they're in their own timezone.

There's a tradeoff between subdivisions per country and the UX that causes for timezine picker dropdowns in making everyone else scroll past all the US, Canada, India etc. subdivisions