"Sending" a file to another disc or on the network is non-transformative. At the far end, it's still a file.
But "printing" is inherently transformative-- you're expecting to get something clearly not a file (print-to-file pseudo-printers excepted).
I can see the desire for minimalism-- having seperate rows for "share/send" and "print" is, well, two seperate rows. But if you offer adaptable and configurable interfaces, I could see suppressing one or both depending on context or user preferences. (You have no external drives or registered share-recipients? No "Send To/Share")
To me there seems to be more difference between sending and share. One is pushing something somewhere, the other implies making it available for someone/thing to pull.
I'm not particularly saying you're wrong btw. We are talking metaphors, and there's no 'correct' way to do it.
I guess printing it to paper is a form of sharing so they may have the last laugh.
Macs have the problem multiple times over, because now they have the normal menu bar and toolbar, and a Share menu that just gets arbitrary stuff dumped into by App Store apps, and the Services menu that shows up in some contexts but not others, and the Quick Actions menu that shows up in some contexts but not others, and some services can just add things directly to right click menus.