Functional equivalence here, of course, depends on the completeness of the test suite, where byte-identical compiled artifacts does not.
(For example, your approach would not necessarily catch all the same overflow behaviors; the OP expressly claimed that "replicating all bugs" was also important, and many bugs are caused by certain overflow behaviors)
Byte exact seems only of interest to preserve known bugs etc for cheats/shortcuts/etc.
> catch all the same overflow behaviors
So you're looking not just for functional but also dysfunctional equivalence %)