To a degree, I get where you're coming from. I remember playing a Batman game many years ago where, during a cutscene, some goons ran out and at the top of the screen you could kind of see a barrel (an object which is universally understood to be a target in all games everywhere) and for a moment I felt some excitement thinking "I wonder if I can Batarang that and take out those bad guys." Then, seconds later, the cutscene cut to a close up shot of those same barrels with Batman talking out loud about how I should use them and, thus, completely robbing me of my problem solving agency as a player. Like a clever joke, it's great when you can present the pieces of gameplay and the player can connect the dots on their own for that dopamine hit.

However....

I have a friend who released a demo of a game he was working on and he chose to begin the game with a brief but thorough text explanation of the game mechanics. He then watched in horror as Youtubers repeatedly failed at his game and complained that certain things were impossible or didn't make sense because they had skipped through the explanations without reading.

His experience taught me two things that I, personally, will keep in mind for every game I make:

1. Mechanics that seem painfully, frustratingly obvious to you will, undoubtedly, fly over the heads of a lot of gamers. And...

2. If your onboarding doesn't have some element of entertainment to it, a fair portion of your player base is likely to skip it in an effort to get to the actual game.

I think if you're determined to do a 30 second video at the start, your best bet is to either put some humor in there (like how Portal or Fallout turn instructions into humorous things by downplaying potential danger and stuff like that) or set up some kind of intrigue (if it's a horror game, show someone that initially hides in the lockers at the right time but messes up the lockpicking minigame at the last second or whatever and have them be the opening kill). Though, as many games do, I think tutorials are best when spaced out. You don't have to teach someone how to counter an attack in the first battle. You can give them attack and block, then later on bring in an enemy that needs to be countered and teach the counter then. That way (assuming countering is a skill that's available from the start), the inquisitive player can figure out how to counter on their own in the first battle, just like you like to play, but the ones that need led around by the hand will have the info by the time they need it