I've always done a menu scene and then a scene per level, with a script that loads the menu first and a start button that loads the level, async when there's a loading bar. the real question is how to structure it for testing, whether the player should be a prefab, and how a prefab references ui that is not part of it. i stopped trusting my instincts and asked what people actually say.
the documented, normal thing is exactly what i do. unity lists the main playable character as the canonical prefab use, placed at the starting point of each scene, and editing the prefab asset updates every instance. the position and rotation of an instance are scene specific by design, that is not an override you need to fight. so drop the player prefab in every scene and move on. no spawn script, no keeping one hierarchy forever. runtime instantiate is for projectiles and moving objects, not a fixed player.
single scene per screen loaded with single mode is the default for a reason, you enter play mode from that scene and see the real state of the game. additive scenes are the divisive one, some people put all managers and ui in one scene and load levels additively, others hate the load order reasoning. for testing exactly what i described, the pattern is a prefab with instance overrides kept minimal, and a sandbox scene that instantiates the same prefab, so the main scene and the test scene share the same behavior source. fix the prefab, not the copy in the scene, and if a scene needs real differences make a prefab variant instead of stacking instance edits.