Broke my VDAs after enabling MCS I/O without caching enabled on machine catalog?

I upgraded an MCS image from 2203 CU5 to 2507 CU1, I used the latest VDA cleanup tool in the process. When installing 2507 I enabled MCS I/O because I was planning to move to an Image Definition (DaaS if that matters), which requires MCS I/O to be enabled.

I did not immediately move to an Image Definition, I updated the master image to my new 2507 image straight through the machine catalog using MCS. My machine catalog does not have the storage optimization MCS I/O option enabled... I am guessing that is where I got in trouble.

The VDAs would reboot and register, then become unregistered, seemed to become unresponsive because I couldn't gracefully restart them, and would cause Workspace to show "retrieving the ica file" instead of loading the application. Fortunately the service group's scheduled reboot halted itself after 50% of the machines failed to launch and I was able to rollback the image.

I cleaned and re-installed 2507CU1 without the MCSIO option enabled and it will go out again during the next scheduled reboot. I upgraded other machine catalogs to 2507CU1 without any problem but those did not have MCSIO enabled on the VDA side, so I'm assuming that's where my issue was.