You're almost there. It's probably not useful to know every framework inside out, but there is a lot of value in being familiar with trends, which often means trying out a small project in a new tech to get a feel for it and then moving on.
What sort of value? Every programming tool (not just framework) requires you to learn different concepts to use it. Each requires you to think differently, which strengthens your toolbox in all frameworks, and learning new things often makes it easier to learn.
There is the potential for professional value. You never know where the community will go or what job listings you will see. For emerging tech, a little side project could mean the difference between getting or not getting a job that uses that tech.
This is like people who penalize people with 4.0 GPAs because "that meant you focused too much on academics".
If you really think it's fruitless, then at worst just ignore it.
I don't have a problem with people trying out things, but I have worked with developers that appear to need a new tech for every project. These people are doing it on work time.
It's like when you see a tutorial learn python in 8 hours. That means you have 8 hours of experience in Python, you don't know it in the same way as someone who has used it for 4 years.