What are the odds that OEM rigs with ADL, WON'T have a toggle in the BIOS, and will effectively, have AVX512 opcodes disabled "permanently". (After, who needs AVX512 in a Dell consumer box, right?)
AVX512, small cores and HT all have performance penalty when they are not used.
Small cores and HT being obvious - if your "ST" task is scheduled wrongly ( on small core when it needs big one, or on HT core when it needs full one ) performance will suffer directly and then suffer once more if it gets rescheduled to proper core that now needs to warm up by rising clocks and taking cache misses.
AVX512 is less obvious, if your software has no support for this instruction set, you pay the tax on every context switch. If you core was working on task A and has FP dirty bits, bad luck for you, now instead of saving 16x256bit AVX256 registers you need to save 32x512bit + mask registers to the thread state on each context switch. That is 4x more data to save that eats into caches.
And context switches do happen on rescheduling, user/kernel transitions and some other cases. They don't happen when you have 1-2 threads per core busy rendering or encoding and thus things look great in benchmarks that support AVX512 and are relevant for barely anyone?
So not having AVX512 is perfectly fine if your software is not optimized for it ( easier to list things that support like rendering, encoding, than all others that don't like games and desktop computing ).
Smart Alder Lake owners will just disable small core clusters and AVX512 and stay with 8 proper cores, while leaving their rendering and e-p competitions to next gen Threadrippers. I will certainly won't cry a single tear about missing AVX512 on desktop, got proper systems to take care of me.