If one is reading mail, a good quality MUA will not be "loading a GIF from a server" in the first place. The content to show should be all right there in the message to start with, included using multipart/, or it does not get shown.
* http://jdebp.eu./Proposals/gnksoa-mua.html#NoAutoFetchExtern...
CSS can cause problems, too. @import could cause privacy issues, as could @font-face. If images are not pre-downloaded, @media and @page could reveal when you print a message and @supports could leak details about your mail client. `position: fixed` would need to be banned outright I'd think, if the message isn't sandboxed in an iframe.
HTML5 as a whole is designed for building applications, not for making pretty messages. You want to have a subset of HTML5, but not too strict of a subset. Some APIs (e.g., @font-face) probably can't be used as-is and need a replacement. And of course, it all needs to be somehow backwards-compatible.