What if instead of creating the transaction there, you just copied the destinations and the payout amounts, and created the transaction in your airgapped device?
That becomes far more clunky and time consuming, as well as error prone. Since the airgapped wallet does not know anything about which inputs to be used, then you will also need to copy across individual inputs and then manually craft your transaction since I don't know of any airgapped wallet which allows you to import individual inputs.
You can also just install a software that checks for your transaction's SIGHASH like Sparrow.
As I said above, although Sparrow lets you chose a different SIGHASH to use, it doesn't actually show you which SIGHASHes were used once the transaction has been created. So importing a signed transaction to Sparrow instead of Electrum does not solve this issue. The only way to know for sure at the moment is to manually examine the transaction data and check it uses 0x01 for SIGHASH_ALL on each input.
It would be a fairly simple change for the preview transaction on either wallet to display the SIGHASH type for each input next to that input.