Believe it or not, some stores sympathise with you. They might actually be run by people like you, people who read your story. They still want to know how you proceed round the store, because that helps them optimise shelf layout, identify hard-to-find items, and so on. So yes, they might use the standard in-store CCTV to observe your journeys, and when they figure that you and people like you always have difficulty…
Sure, it may be frustrating when a user blocks tracking tools (especially self hosted ones) but that's the their choice.
We got by for decades without analysing user habits (even in a local only context, without correlation with third party data). There are so few examples of cases where analysing user behaviour was a make or break factor in a store's survival. Sure, it can be useful to know what a user looked at and, as you suggest, how difficult it is to find the eggs. But there are better ways.
Physical stores at one point (and still now, in many cases) respect that user choice. Want to participate? Get a loyalty card. We'll watch how you spend, but we'll give a little something back to participants.
On the web, the solution is simple. Do it on your application servers back end. Have your request handler (which should probably know a lot more about your user in the context of your application than any third party tool) log user requests and actions. You'll be able to tie data gathered to a logged in user and their local purchase or browsing history.
You'll get to know your user better and you'll avoid third party tools that creep out a growing proportion of your users.
You're not entitled to participation in analytics.