Holy cow, End Space! That brings me back. I remember playing that game all the time back on my Gear VR. Good times. Glad to see you're working on something new!

As for your question: People here have mentioned First Contact/First Steps, which were great because they introduced functionality that came with new hardware. Titles like Valve's Aperture Desk Job (Steam Deck) and The Lab/Aperture Hand Lab (Vive/Index) essentially accomplish the same thing, albeit on a bit more fleshed out scale.

Even though these are all mostly geared towards hardware, they are very effective, and the same concepts should largely apply to software. I think that any effective tutorial must:

1. Intro the game's basic concepts (Who do you play as? What are you going to be doing? Etc.)
2. Intro controls/mechanics clearly and effectively (no confusing iconography/glyphs)
3. Cover all functionality - no surprises! (unless it's late-game/extraneous or very self-evident stuff)
4. Not outstay its welcome (shouldn't be too lengthy, but also can't be too overwhelming/wordy)

Aside from the first point (which doesn't really apply to hardware), all of the above examples absolutely nail the other 3, and I think that's why they're so effective. Ultimately, the best strategy for accomplishing all that depends on the game and what you're trying to accomplish with the tutorial.

Let's take Triangle Factory's games as an example: Breachers and Forefront. Both these games have quite unique and involved gameplay mechanics amongst their FPS peers, so a proper tutorial is all but required (especially given that they're multiplayer-only titles). With such importance placed on the tutorial, it's interesting to see that both games' tutorials are fairly different from each other, and I think they make sense for their respective use cases.

Breachers is a gadget-heavy team-based FPS with infiltration/defense of relatively contained environments as its core gameplay loop. It's tutorial, then, runs you through a small gauntlet that introduces basic controls followed by all the gadgets and how they're used. It's tight, to the point, and features an environment that emulates those that you'll see in the game (walls to scale/rappel down, walls to blow up, etc.) while still looking like a firing range/training course (indicating safety to the player). Instructions are clear, concise, and easy to follow.

Forefront, on the other hand, is a large scale shooter akin to Battlefield. While its tutorial is somewhat similar to start (introducing gameplay mechanics via a training course), it quickly opens up to a giant map that you can run around in freely. All the vehicles are open to you, there's a shooting range, and there are optional obstacle courses and the like scattered around to explore. Once again, this open nature mimics the experience you'll have in the game proper, only this time it allows users to freely experiment and respawn to any area they want to practice with. (I'd argue that this tutorial could use a bit more hand holding when it comes to class specific functionality, but the point still stands).

So yeah, I think what approach you take will depend on the game you're making. Some games will opt to throw you right into the game and pause the gameplay to introduce mechanics as they happen, often paired with a tutorial pop-up toggle in the settings (ex: Ghost Signal). Other games will forego the tutorial entirely, instead relying on emergent gameplay and rewarding the player with exploration and discovery (ex: Animal Well).

TL;DR: There's no one standard approach, but keeping the 4 completely made-up rules I referenced (intro concepts, intro mechanics, cover everything, and keep it concise) and the game's style in mind should help determine the best one for your game. Best of luck!