You can do scripted multisig with P2WSH which has addresses that start with bc1q. Scripted multisig makes use of OP_CHECKMULTISIG and lists all public keys and signatures separately. With MuSig2 you would be using P2TR addresses that have the same length as P2WSH and start with bc1p. MuSig uses scriptless multisignatures. All the public keys are aggregated into one and you will only see a single aggregated signature in the corresponding input. As such they are indistinguishable from single-sig uses of P2TR. P2TR outputs can also have additional spending conditions defined in their script tree which can contain scripted multisig constructions. Those would then make use of OP_CHECKSIGADD instead of OP_CHECKMULTISIG.
OP_CHECKMULTISIGand lists all public keys and signatures separately. With MuSig2 you would be using P2TR addresses that have the same length as P2WSH and start with bc1p. MuSig uses scriptless multisignatures. All the public keys are aggregated into one and you will only see a single aggregated signature in the corresponding input. As such they are indistinguishable from single-sig uses of P2TR. P2TR outputs can also have additional spending conditions defined in their script tree which can contain scripted multisig constructions. Those would then make use ofOP_CHECKSIGADDinstead ofOP_CHECKMULTISIG.