I think picking the sender (let’s call it “Designated Sender”) will be one of the key problem to make this Progressive approach work.
The ultimate promise is that: All EVM chains (including future EMV chain that don’t exist today) shall be able to deploy with the identical address of Designated Sender.
That means there needs to be a consistent way for that Designated Sender to come into existance in new chains, in all constraints to these chains.
For example, if a chain is designed to be permissionless, the Designated Sender needs to come into existence in a permissionles way. For example, if the one that you suggested, which is the Default Foundry Factory 0x4e59…956c that you referred to is created in the TX by The Wolves of Wall Street: Deployer 0x3fab…5362,
Which means the Wolves of Wall Street Deployer might have to publish they private key so new chain could establish them, which could have security implications.
Therefore, it seems so far, the sender itself needs to be a precompile (or have its own address), as proposed in the thread proposed by @spalladino