If you're not aware, the HTTP protocol specification[1] doesn't have a technical way of knowing ahead of time if it's a 1x1 tracking pixel.
So the remaining realistic options are:
(1) block ALL <img> tags downloads which then blocks any 1x1 tracking pixels
(2) allow <img> tags but block some (and maybe most but not all) 1x1 pixels via a blacklist of url domains (e.g. doubleclick.net) ... and/or heuristics based on the "style" attribute
The (1) already happens in many email clients that render HTML.
The (2) is happening with the ongoing cat & mouse game with AdBlock, EasyList, etc
[1] https://www.google.com/search?q=http+protocol+request+get+sy...