Seems like a fairly nice way to approach this (as long as it can also be disabled in the options). Heck, might as well have reverse image search context options for all the search engines that support something like it.
The alternative is to use a meta-search engine which uses all of the above without feeding these data parasites any personally identifiable data. There's plenty of those to choose from; I use SearXNG [1] which forwards my queries to a number of engines and presents the results - and with that I mean the actual results, clear from tracking links etc. It is not perfect in that there's a persistent issue with search engine timeouts which is quite irritating but I'd rather wait a few more seconds for search results than feed the data parasites.
I prefer Google Lens because the voodoo it does is far more than just image search, and is genuinely useful to me. I use it to translate text in images multiple times a day (I live in a country where I'm not a native speaker). I've used it to identify birds, plants, and even furniture - it found me the local shop for a table in a cafe that I liked, which was pretty amazing.
I'm not a Google fan, in fact I actively try to choose alternatives where possible, but they do make some good products not matched by anyone else, and it's not useful to pretend that isn't the case. Lens is one such product, Maps is another... Ok maybe that's it, since I use LLMs for most translation tasks these days.
If this sticks around I hope (and mostly trust) that they'll make it configurable across different image search tools.
Other than that this seems... fine. Good even. It's a nice to have feature that isn't in the way and presumably doesn't share any data at all until you explicitly tell it to.
Good feature. Searching an image is already an older mode of Google Lens. Chrome currently allows you to search any region, which is more useful for searching something from a video frame or a portion of an image. Not sure why Firefox would implement the older version.
This isn't really an antifeature. If someone has Google as the default search engine I doubt they are going to be against this. If you don't have google as the default you won't even see this.
I mistakenly blamed Brendan Eich for some general Mozilla idiocy that I now see as really being due to Mitchell Baker. Sorry Brendan. I can blame Brendan Eich for some technical deficiencies in early JS but that's way less far-reaching.