Who knows but I doubt it.

It's probably more about people complaining they can't run Next or some other framework on Deno which directly impacts their business (Deno Deploy).

Doubt it too, because -if I remember the public discussion correctly- how to migrate projects over from node to deno without basically rewriting anything was a question straight from the beginning. And bun was not a thing, or was it? - First bun 1.0 release was 2023, deno 1.0 2020.. so maybe, but unlikely :)

Anyways, that backwards compat is huge

Deno has had node compatibility for longer than Bun has been announced

It's always been controversial in the deno compatibility since they originally promised to take a principled stance NOT to support node in order to move the scene forward. But they quickly realized that they were in a market and they needed to compete and backtracked on that almost immediately