Injecting the VM isn't an optimal solution, as it exposed the view's internals to the outside world. That complicates each and every call site that might want to display the view, while at the same time making it much, much harder to refactor the view should the need arise.

Further, your last example is problematic. Your passed VM is what's used as that overrides the assigned, thunked wrappedValue. But that thunk is only called once for the lifetime of the view, which means that it can't be "reset" to to "new toggle".

That's unexpected behavior.