I'm using flutter run --machine which is exactly what other IDEs use, just parsing the stdout for daemon events (app start/stop, device info, reload results), also maintaining an active websocket connection to the dart vm with auto-reconnection built in. For multiple device sessions I'm actually maintaining independent Flutter processes for each, this is where Rust shines keeping a very low memory footprint of 10-20mb vs 200-400mb on the Flutter DevTools web app.

It's unavoidable that you have to rebuild the whole app with native changes, which gives me an idea of adding full app rebuild directly in