Repair GTID from Restore with sql_log_bin=0 and then drop table
The issue is that you have this blob of data that was no way of being replicated.
When you put it on the master and it set the gtid purged variable it basically says: I have this data, but I can't give it to you. 

What you can do here is to use this dump to provision the slave/secondaries servers. 
So you can execute this update in the master, but when you add a new member before it joins you must also execute the dump there. 
Then they both can say: we have this lump of data we cannot replicate so we are in sync. Then the joiner can fetch whatever it is missing from the primary .