Aggressive optimization of `unreachable`s?

I have written a Binaryen pass that emits unreachables into the wasm tree. That produces something like this:

 (func $17 (param $0 i32) (param $1 i32)
  (block $label$1
   (br_if $label$1
    (i32.eqz
     (local.get $1)
    )
   )
   (br_if $label$1
    (call $26
     (local.get $1)
     (i32.load offset=32
      (i32.load
       (local.get $0)
      )
     )
    )
   )
   (drop
    (i32.load
     (i32.const 3308276)
    )
   )
   (unreachable)                 # Added by my pass
  )
 )

Since the end of the function $17 is unreachable, I'd like an optimizer to realize that all the preceding statements are then unreachable as well since the control unconditionally flows to that unreachable. So the function could be collapsed into a single

 (func $17 (param $0 i32) (param $1 i32)
   (unreachable)
  )

and then further inlined into its callers, and the unreachable propagated that way to their callers and their callers, as efficiently as is possible.

I was trying to run different optimization passes in wasm-opt, ranging from --dce, --inlining-optimizing, --O4 and -Oz and pretty much anything else that had a summary description that it might optimize something,

--inlining-optimizing --dce --coalesce-locals --code-folding --code-pushing --const-hoisting --dae-optimizing --duplicate-function-elimination --local-cse --once-reduction --optimize-for-js --optimize-instructions --optimize-stack-ir --post-emscripten --merge-blocks --merge-locals --merge-similar-functions --remove-unused-brs --remove-unused-names --remove-unused-module-elements --remove-unused-nonfunction-module-elements --reorder-locals --rse

to see if one of the existing passes would get aggressive with throwing code away when there is an unreachable on a potentially critical path. Reading the code in dead-code-elimination pass seems like it would do something like this, however I find it being unsuccessful with modifying func $17 above.

Is there a way with Binaryen to have func $17 get nuked from orbit altogether due to its unreachable, and everything that would ripple to?

Attached the .wasm file that contains func $17 if it is interesting to take a hands on peek: ozm.zip.

Start by reproducing the example with wasm-opt and the attached ozm.zip, then read the dead-code-elimination pass and the listed optimization passes. Determine whether an existing pass can collapse the function to unreachable and propagate that result through callers; done means documenting the supported behavior or defining the required optimizer change.