Depends upon what the "1" , "2" , "3" means in the M1 , M2 , M3 name.
If it is 1st generation architecture, 2nd generation architecture , etc. Then if Apple primarily just shrinks the N5P core designs onto N3 then it technically could still be M2. The fab process and the general architecture don't have to be coupled.
Intel used to run Tick / Tock model.
" .. Under this model, every
microarchitecture change (tock) was followed by a
die shrink of the process technology (tick). .. "
https://en.wikipedia.org/wiki/Tick–tock_model
It is a risk management strategy where only change one major attribute at a time so that have more ability to work around problems (i.e., more time to 'focus' a manageable set of issues. ) . Yes, Intel marketing slapped different names on those phases. But if are going to overlap in less than a year time ... you don't really have to. Actually, probably better not to.
Apple already did this once.
P and E cores Hurricane and Zephyr on 16nm on a large very bloated for an A-series die 125mm^2
en.wikipedia.org
[ For perspective the M1 is 119mm^2 . The average iPad Pro die over last several years was around 120-125mm^2 ]
P and E cores also Hurricane and Zephyr on 10nm on 96mm^2
en.wikipedia.org
[ a bit under usual iPad Pro die A9X 145mm^2 , A12X 127mm^2 ]
The A10X was the first major die design rolled out on 10nm. Turns out smaller than the A10 .
So suggestive that the number is mainly being used to talk about microarchitectural generation; not fab process.
But it is N3 , Apple can add "more cores" , more , more , more. That has an underlying presumption that N3 is easy to work with. That may not be the case. Given that TSMC is shifting to be back half of their 2H '22 time window is suggestive it is not super smooth sailing. And that might have had early indicators years ago ( if looks tough give ourselves an extra ,extra wide time window to hit). If getting onto the process is expected to be a bumpy ride than Intel's old tick-tock model is a pretty sensible move. Don't do major changes to the arch when move to new process. It is way less risky than messing with multiple dimensions at the same time.
TSMC has already mentioned that they are trying to pull forward a N3E process that is "enhanced" (which may just really be "easier to work with and get decent throughput through the fab " . ) Going to be a fair number of major players that are going to skip plain N3. ( AMD , Nvidia are just landing on N5 and N4... they could skip the initial N3 later just like Nvidia (and Qualcomm) are skipping N5 ).
Apple could add something like AV1. Limited scope , fixed function logic have been working on but never had enough "extra space" could be weaved in. ( Intel's ticks usually were never completely empty of any improvement. ). The major function blocks are just tweaked to be smaller. And they would have lots more leeway to crank boost clocks for single threaded drag racing "fun". If the Max size shrinks it would be easier (probably incrementally less expensive) to do two die Ultra packages. (could even just get rid of the chiplet path and just do monolithic "Ultra". If N3 is finicky then perhaps not. ) . Certainly, the quad die solution gets substantially more tractable if primarily focus on shrinking the Max class size dies.
They likely would not end up with a Intel/AMD desktop CPU package killer solutions at the higher end. However, they would be very competitive for lots of workloads. Wouldn't have a 4090 or 7900 killer GPU either, but competitive over a wide range.
Make it work. Then make it fast. With N3E, they could grow the Pro/Max/Ultra back up the current sizes. A "tock" phase.
After N3 (and its suffix variants ) comes Gate-all-around which likely will be another shift where could probably substantially lower risk by getting it right before going "buck wild" on microarch changes. Because shifting the arch those could be tagged M3. (and start trickling some of those out in 2024. Also not waiting around for N2. )
If A14 , A15 , and A16 are all on ever bigger N5 family dies that too could be due for a "tick" shrink with A17. Those are bloating way out the normal range like the A10 did. Also about the time where a new relatively very large modem subsystem is possibly either being weaved onto die or into the same package. Verson 1.0 of the modem probably makes sense to keep discrete though. At least a chunk of it.