In principle, if you have automatic image loading "On", it should load all images, and the moment the image is loaded, tracking happens. I don't know if Kostya implemented anything special here.
Usually, the tracking pixel is an image that has a 1x1 size. It would be hard for the app to know how large the image is without sending an HTTP request "GET", which IS the "trackable/tracking event".
How can an app distinguish tracking-pixel images from the rest?
1. By the size, if that is specified explicitly ("height=1, width=1"). I suspect that the mail-tracking providers are not that stupid to leave the Jolly Roger out there.
2. By the URL:
The URL has several parts: the domain name, the file name, and parameters.
The file name is often unique for each message, which allows tracking of the individual message.
Sometimes, it is the parameters that contain the unique identifier of your message.
So, in general, you cannot reliably figure out that it is a tracking pixel based on these two parts.
Domain name may or may not contain unique information. But even if it does contain a unique portion (typically a 3rd level domain) Typically, the 2nd level domain portion would be the same (pertaining to the company), i.e.
http://third.second.first , e.g. aq8wdb9.trackingmail.com
So, that portion can be used by ad-blocking/privacy apps. AFAIK, Aquamail doesn't do any filtering of that sort. If your tracking pixel is blocked in Aquamail despite the automatic loading of images enabled all the way, - I'd expect you have one of those apps installed.
Now, the reason why loading Gmail in Chrome (and, quite possibly even in Gmail app) might not be affected by the ad-blockers is that Gmail would be loading those images on their server is loading those images first, and then feeding them to you and your web-browser (or Gmail client). So, the image has been loaded BEFORE the ad-blocker could do anything about it.