So, if it's a PCI 2.2 compliance issue, then I don't think it's VIA's fault.
Both the SBLive! and SBAudigy list as their system requirements "PCI 2.1 compliant slot". Not PCI2.2. If they required "bus parking", then they have misrepresented their products requirements. Looking at Netgear, their current products list 2.2 as a requirement, but previous products only list a PCI bus with bus mastering, which doesn't mean 2.2 is required, so again if there were problems, it wasn't VIA's fault. Same thing with Adaptec cards. Promise cards indicate *either* 2.1 or 2.2 slots are required.
In fact I don't think any of the devices I have ever used have specified a requirement for PCI2.2. If they said anything at all, it was that they required PCI2.1 compliance (many only specify they require 32 bit PCI with bus mastering). Until today, I didn't even know that there was such a thing as a consumer board with PCI2.2.
Looking at motherboards, many don't seem to specify whether they're 2.2 or 2.1 compliant, even in the manuals and spec sheets. However Asus lists the A7V333 as being 2.2 compliant, which uses the VT8233A southbridge. Again, not VIA's fault if the motherboard manufacturer doesn't include specifications regarding PCI compliance.
VIA's own website is sparse on information about the PCI bus, they never seem to list anything regarding version compliance (one can draw one's own conclusions about why).
As far as I can tell, it's not really VIA's fault, if bus parking is in fact the problem. They never claimed to have a part with compliance for the 2.2 spec which included that. Nor do most mainboard makers seem to even mention what specification their boards comply with. Nor do most card makers even specify that they require a 2.2 compliant board. If they are including this requirement, then they are doing so outside of the 2.1 specification, making it their fault if it doesn't work with a 2.1 compliant motherboard.