Overall, this approach seems reasonable to me, given that the new wow isn't possible in this case.
We might consider swapping the loader naming in this scenario. For instance, the default `wine` could serve as the 64-bit loader (also handling x86 emulation), while something like `wine32` could be used for 32-bit ARM. This would make it easier to package 32-bit ARM separately as an optional addition to the 64-bit Wine package, avoiding dependencies on 32-bit host libraries for users not interested in 32-bit ARM.
(I don't think it's a blocker for this MR, I'm just suggesting it for consideration.)