Why go for a specific implementation for contract creation and native tracer (traceTransfers). Just give the user the full transaction traces. The foundation can describe an example utility code for extracting these “events” from raw traces, which gives maximum flexibility for all use cases
The goal of this spec is to "enables simulation of complex transactions", however it is still lacking existing functionality in debug_traceCall. For example, the Bybit Exploit (mainnet - 0x46deef0f52e3a983b67abf4714448a41dd7ffd6d32d32da69d62081c68ad7882) cannot be detected in this proposed RPC, as I understand that eth_simulateV2 doesn’t contain storage state diffs (pre, post)