What's wrong with the daily? Why teams want skip it?

I've heard something alarming from a couple of teams i had the honor to serve in past and current days.

They want skip daily the day after planning!

For me it's an absolute no-go, but why that's happening in different teams is the question? Is it just a coincidence?

So I asked the same question to other Scrum Masters and in a well known group of scrum experts and I got different interpretations.

Some scrum masters told me "why not skip it if the team like it?" or "if is the day after the planning they don't have much to sync".
And asking team members I got answers like that: "since we had the planning yesterday we don't have nothing to report" and defend the position with "we agreed that with the former SM, why you bother us with that question again?".

I got the idea those guys think at the daily just like a report.

What I learned as SM and former developer is exactly what's written in the guide, the daily serves to plan the today's work:

The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

For me that's simple, the daily is a must and should be done in each day during the sprint.
Of course not when one of the other main events like review or planning occurs in the morning (or at the daily time in general).

But again why this doesn't happen right now?

I think, it's because the "3 question approach" is interpreted like a sort of report, and often in direction of the PO instead of the team.

How can we have a more useful daily? I think a solution is to find another "structured" way to help the team mates. In fact the current is a very simple template to follow. Can we build another simple template but more collaborative one?