Adding WASM support to FATE sounds more future-proof to me than becoming EVM-compatible, though @hanssv.chain can probably estimate better whether that’s a realistic undertaking or not.
In general I like the idea of becoming more interoperable. Also WASM seems to be much faster than JS on several browsers/devices (30% faster on Chrome, 60% faster on mobile and 90% faster on Firefox) according to How fast and efficient is Wasm? (study from September 2021)
What would that mean? FATE is the runtime engine for aeternity smart contracts (expressed in FATE byte code) - making it also run WASM makes little sense?! 
Porting/translating/transpiling FATE to run in/on WASM could be done, but since FATE includes instructions for interacting with the aeternity chain in many ways you would need to have more or less the whole node running in WASM. Certainly not impossible, but it would be huge undertaking.
as discussed in our workshops pre-conference @radrow.chain will do some research on the WASM topic and we will publish the result through our communication channels (including this thread)
apart from that we will analyse if we can provide a more elegant way to “copy” frontend applications more easily from EVM based chains by providing similar API to a widely used library like e.g. web3.js or ethers.js - we’re not sure if this is doable but right now there is no easy way to do that. frontends more or less need to be entirely rewritten and adapted to æternity like we experienced with the Superhero DEX UI implementation.