Well, kinda. But it's been a few years since it really did. It defaults to "show then what we guess they want rather than what they literally asked for".
Most people are absolutely terrible at keywords based searching. Which is not very surprising since most people are terrible at spelling out what they search to begin with, and they're also terrible at turning a sentence into its important keywords, so doing those two things at once brings all the bad.
To this day, even with current Google helping them out a ton more, I'm still amazed at most people complete inability to type out what they search for in any meaningful way.
Pay attention to how people ask their question when looking for something and you quickly realize they don't ask their question in a logical way, or using the words you would expect. Pay attention to how many time when someone ask you something you feel like saying "What are you actually trying to find/do/achieve ? What is actually your issue, instead of the half-way mess you just said that made no sense ?". And people are also really bad at realizing that and taking a step back, and tech user are not exempt; something like half of stack overflow question are broken that way (totally made up stat).
Then add a layer of "this is a computer I need to computerize my query !" and you enter the land of weird.
PS: with that said, allowing a full verbatim mode AND an option to keep it activated at all time for my account would be totally awesome
You can mostly solve this by creating a keyword search that launches a verbatim search. Depending on your browser, the syntax probably looks something like this (with the essential part being the 'tbs=li:1'):
Of course, this still leaves the problem that verbatim on Google doesn't always mean 'verbatim' anymore, but that part will have to wait until Google changes their ways (unless you put quotes around every word).
This is the same reason clicking once on the address bar in Chrom(ium) selects the entire text, and two clicks narrows it down to a single location - which seems the reverse of what usually happens. The design justification for this on Monorail was something like "most people use the address bar to perform new searches", instead of editing the URL they were already at, so it was better to save them that one click.
Current attempts to try to make everything a conversational AI are pure failure. Whoever is in charge of Siri/Alexa/Googlette/Whatever thinks people are saying "hey X, do Y" as if talking to a human. In reality, those people are trying to figure out the magical sequence of words and intonations that will make the thing do what they want, frustratingly and poorly reverse-engineering some inhuman and constantly-changing robot.
Other examples that bother me: randomly, I don't see my flights in the Google Assistant on my Pixel. I then have to type "My flights" in the search box to see them. Same for weather, hotel bookings, etc.
Sure, you are right, and moreover Google could interpret the request as an AND; but they don't return results that _correctly_ fulfil such a query.
So, practically the distinction seems useless?
To recapitulate, it's not my interpretation that the results don't match a logical AND, it's a fact.