Template vs Content Editing UX: always default to Template Editing on first load

[liviopv]

What problem does this address?

With the introduction of #50857, the Site Editor will default to content editing if a page is assigned as"Homepage" in Reading Settings
Considering the link to the Editor lives inside "Appearance", I'd expect that I'd be able to edit appearance-related elements as a first option. Instead, I'm taken directly to content editing, which feels out of context and adds friction to actions like managing a site's navigation, editing header and footer elements, and adjusting the layout.

What is your proposed solution?

Template editing should be the default experience in the Site Editor on the first load, regardless of other settings on the site or the template is loaded, since there are two other highly-visible paths for content editing (Page Editor, Site Editor > Pages).

Alternatively, default to content editing/default to template editing could be defined at the theme level or a user-facing setting for even more freedom.

[rickmgithub]

Adding to the comment above. I would love to see the options in the site editor be part of the main menu.

e.g.
Pages
Post
Templates

Right now if I am editing the home page there is a good chance I'm in the site editor. Getting from the site editor back to say my "about" page, means clicking to go back to the site editor menu, working your way back to wp-admin dashboard, then clicking pages to open the list of pages. It would really reduce friction if I could do that in one click.