Define everything in like cdk (... I use ruby to generate the tf.json), generate the code, import everything you can without error, and apply the rest.
Performance will be _bad_ but that will completely eliminate state problems.
CF tries to create as many resources in parallel as possible based on the dependency graph it creates.
The only way around it was making each Parameter resource dependent on the other (using DependsOn) to force the resources to be created sequentially.
Before the CF vs TF holy wars began, this is an API limitation that you would hit regardless of your IAC.
cdktf is great, but I would also rather do away with the state. I’ve gotten into too many problems that were only resolved by deleting everything and starting over.
I use this today to keep very “wide” modules synced