If they mean a common pool where deposits, notes, and spends are enforced by the protocol rather than by a contract wrapper, thats more than a mixer rename. Do deposits and withdrawals stay unlinkable across the L1 bridge and paymaster path, or is the privacy only inside Starknet after funds are already in the pool?

If the pool is enforced by the protocol, the useful bit is that notes and spends stop depending on one contract’s bookkeeping, so you get less room for wrapper bugs and “oops, that mixer got upgraded” nonsense. The part I’d still want spelled out is exactly your bridge point, because L1 deposit and withdrawal transactions are usually the easiest place to stitch identities back together, and a paymaster can leak patterns too if fee payment is tied to the same account flow.