What you call «the new Apple way», RichardTS, has been available on practically all email clients since the ‘90s, when it became an Internet standard!
(At about that same time, the old plain-text [text/plain] email format began to go extinct.)
In all cases, by the Internet standards, added files (including images and photos) are attachments!
The issue is that only a single email client (and its derivatives) prevents its users from performing bulk attachment operations (such as bulk-saves) based only upon how that email client chooses to display (render) your received emails.
(I challenge anyone to find another email client [that is not a derivative of the aforementioned errant email client], with this errant behavior.)
This means that anything any other email client may attempt, in order to try and make that single, errant email client “do the right thing”™️, is doomed to being fragile: easily broken by tiny changes anywhere within the web of interactions involved in transferring emails.
The only guaranteed means for solving this issue is for the manufacturer, of that errant email client, to correct it, to allow you, the user, to performing bulk attachment operations (such as bulk-saves) regardless how that email client chooses to display (render) your received emails.
This is what all other email clients (that are not derivatives of that single, errant email client) allow their users to do!