Feels slightly pedantic to point this out, but this describes an emulation stack. A lot of emulators are already doing some kind of lift+JIT on the target's machine code (just not through WASM)
https://github.com/jessicanataliagta/PSPRecomp/blob/main/src...
The original hardware doesn't exist on the target system.
Taking a famous example out of many others I could have reached for,
> Emulation had been around for a while as a concept, but FX!32 went one stage further. It analyzed the way programs worked and, after the program ran, used binary translation to produce dynamic-link library (DLL) files of native Alpha code that the application could execute the next time it ran. This way even in the early 1.0 release, the FX!32 achieved speeds for Win32 x86 applications that ran 40-50% as fast as native x86 code, with a 70% speed projected as likely with improved optimization. Version 1.5, released by Compaq in 1999, added support for the Alpha 21264 (EV6) CPU, including emulation of Intel's MMX instruction set.
'Emulation' is a general English term applicable outside digital systems.
A group of people had problems and solutions that required an expanded vocabulary in that space, and they choose to re-uses the generic term to be a specific technique, and to use other terms for other techniques.
You're complaining that this doesn't align with your memory of a different group of people who picked different.
Complain all you want, but this is just how language works. The kids playing Roblox right now will grow up, and replay this whole spiel in their own way.
According to WINE itself, WINE is an emulator.
Ultimately there's a spectrum between emulation and native code and where you draw the line is an arbitrary and subjective choice.
https://github.com/jessicanataliagta/PSPRecomp/blob/main/pro...
> That code runs against a register file and a model of the PSP's memory.
From the project README. That to me, is an emulator.