xpub – Is the trailing pathing in multi-sig descriptors crucial?

I created a multisig pockets with BlueWallet, and I need to convert the config file to a descriptor:

Identify: Multisig Vault
Coverage: 2 of three
Derivation: m/48’/0’/0’/2′
Format: P2WSH

1E74CA69: xpub65……………………Qwg1Wd

9F40E694: xpub74hnJ……………………cWoEszidc

derivation: m/48’/0’/2’/2′
B5B630B5: xpub6F9A……………………Rb1VjK

I see within the docs that when making a wsh(sortedmulti()) descriptor, the keys normally have trailing pathing (instance: [e6807791/44h/1h/0h]tpubDDAfvogaaAxaFJ6c15ht7Tq6ZmiqFYfrSmZsHu7tHXBgnjMZSHAeHSwhvjARNA6Qybon4ksPksjRbPDVp7yXA1KjTjSd5x18KHqbppnXP1s/0/* —> Right here I’m speaking concerning the /0/*). I additionally noticed within the docs that you simply need to make 2 descriptors; 1 for change addresses and 1 for normal addresses : "Now the multisig is created by importing the exterior and inside descriptors: wsh(sortedmulti(<M>,XPUB1/0/*,XPUB2/0/*,…,XPUBN/0/*)) and wsh(sortedmulti(<M>,XPUB1/1/*,XPUB2/1/*,…,XPUBN/1/*)) (one descriptor w/ 0 for receiving addresses and one other w/ 1 for change)." Is that true? Or can I simply ignore fully the trailing pathing and simply do:

wsh(sortedmulti(2,[1E74CA69/48’/0’/0’/2′]xpub65……………………Qwg1Wd,[9F40E694/48’/0’/0’/2′]xpub74hnJ……………………cWoEszidc,[B5B630B5/48’/0’/2’/2′]xpub6F9A……………………Rb1VjK))