Slower ramp than what? I don't think there were any viable alternatives to Apple not using N3B. This seems like a lemons -> lemonade situation.
Slower than if multiple customers were each paying for full wafers at a faster pace.
If early on, Apple orders 5K wafers , company B orders 5K , and company C orders 5K wafers then that is an aggregate pile of 15K wafers providing feedback.
If that falls back to just TSMC covering just the 5K wafers than Apple wants than it is just 5K aggregate. Apple isn't going to get more early dies back just because no one else is asking for any. And TSMC sure isn't going to throw away even more of their own money handing Apple die they didn't ask for.
While TSMC has their own 'test mule' designs they push through for development, then will get different feedback by pushing different designs through the process. If just building simple SRAM or simple Arm core were enough to expose all the bugs in N3B , TSMC could have go live sooner. Testing bias pops up all the time within homogenous organizations.
The smaller the sample size, the less robust feedback going to get out early parts of the ramp. The N3B takes months longer to make than N7 or early generations. So the whole cycle is slower. Dropping out other folks generating useful data early only makes for a much longer feedback cycle to generate enough data to be very useful.
TSMC doesn't need 10's or 100's of different designs , but need more than just 1-3.
Additionally, Apple didn't 'need' max full wafer output flow until June . If there were another customer with an earlier timeline they would have higher flow demand in Dec-January (when Apple isn't really all that interested. ).