DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata.

This issue was reproduced against dyn-future 3.0.4 under Miri. And the crate is unmaintained.