[tukz]

Roth, if you are using your own raid unit frames, which I think you do, you can still avoid this taint by telling the client to never create CompactRaidFrame1, CompactRaidFrame2, etc.

This is what i use to disable Blizzard raid/party frames since addon are enable from Beta. I never ran into any taint with raid frames.

	-- disable Blizzard party & raid frame if our Raid Frames are loaded
	if C.unitframes.raid then
		InterfaceOptionsFrameCategoriesButton11:SetScale(0.00001)
		InterfaceOptionsFrameCategoriesButton11:SetAlpha(0)
		
		-- raid
		CompactRaidFrameManager:SetParent(TukuiUIHider)
		CompactUnitFrameProfiles:UnregisterAllEvents()
			
		for i=1, MAX_PARTY_MEMBERS do
			local name = "PartyMemberFrame" .. i
			local frame = _G[name]

			frame:SetParent(TukuiUIHider)

			_G[name .. "HealthBar"]:UnregisterAllEvents()
			_G[name .. "ManaBar"]:UnregisterAllEvents()
			
			local pet = name.."PetFrame"
			local petframe = _G[pet]
			
			petframe:SetParent(TukuiUIHider)
			
			_G[pet .. "HealthBar"]:UnregisterAllEvents()
		end
	end

Unfortunately, i don't think it will resolve the issue if the player want to use default raid frames. (I'm not sure about this, I never tested it.)

And it still doesn't resolve the taint when you inspect someone, and after try to change/remove/switch a talent.