Updater does not retain start parameter

When the client updater restarts the client, at least some of the start parameters are not kept. In particular, on Linux, I start the client with --ozone-platform=wayland --remote-debugging-port=9922 to run it as a native Wayland window and with remote debugging enabled. After an update, however, the client starts without these parameters, leaving me with a broken X window (due to a bug in the X server on Wayland). I thus need to restart the client again manually to fix this.
It would be nice if the updater simply used the same cmdline to start the client after an update.