I do not think so, the moves will get significantly simpler. Walk the uploads table and upload all files to new s3 bucket, rebake and you are done.
They do though become more expensive computation wise cause a rebake is required.
This is a cost I think is worth bearing given we get a correct move at the end of the process. But, we have the flexibility of still doing database replace
as we do today for the cooked column and post revisions if that is how we roll, the key change in the process is that we leave posts.raw alone and then have 0% of corruption there. posts.raw and posts_uploads auto generated map will always be stable.