Like, if new order starts drop by 4% while traffic remains constant, what happened? If that happens, you might want to see if people are using the menu more because something got harder to find on the page.
I doubt anyone is looking purely at menu opens as a metric, unless maybe trying to reduce it. But for ongoing funnel and ad hoc investigations it could be useful. So you collect it.
The obvious answer is sampling rather than collecting for every user, but then you get into complicated statistics about required sample sizes if you want to correlate multiple actions across tech and demographics. Again, easier to just collect it all.
E.g. somebody is complaining that the hamburger menu doesn't work, and then you can go deep into the analytics and discover that no hamburger-menu-open events get fired on a certain version of a certain browser. Now you know what to test and fix. Without analytics for everything, that would have taken a lot longer to track down and might not have gotten fixed at all, because it would just be something intermittent you don't know how to reproduce.
The stunning part is one of these is to get a string of text that is displayed in a banner that is only visible if you scroll in the menu (like, at the very bottom). You could easily defer this call to happen once the menu is open and have 0 impact on the UX.
The other call, I have no idea what it does, but is launched both when you open and close the menu.