No, that sort of thing happens at the kernel level. Can't blame pulse for that.
To avoid this sort of thing, you want to create yourself a sound.conf:
Code:
test@ws1:~$ cat /etc/modprobe.d/sound.conf
options snd slots=snd-hda-intel
options snd-hda-intel id=PCH index=0
options snd-hda-intel id=HDMI index=1
Obviously, if your sound hardware doesn't use the intel driver you'll need to modify it accordingly.