Apparently not in HTML5, although major browsers retained it for the purpose you mentioned and back-compat.
https://stackoverflow.com/questions/11928566/img-vs-image-ta...
https://stackoverflow.com/questions/11928566/img-vs-image-ta...
I discovered, the hard way, that the Android Gmail client, using naked HTML (with a default naked DTD specification), does exhibit this problem. It only responds to <img /> [i.e., not <image />]. gmail.com is fine with <image />, but not the Android gmail client.
Looks like a fingerprinting opportunity to me.
https://www.w3.org/TR/2011/WD-html5-20110113/tokenization.ht...
(Search for "image")