Floating selfip GARPs when virtual-addresses are set to disabled and no arp

I migrated a configuration over from a physical F5 to a virtual F5 with enabled no and arp disabled on the virtual-addresses. Self IPs were configured and interfaces were enabled on the virtual F5 which they probably should not have been. I loaded the configuration via tmsh from a file and used merge even though the F5s were a blank slate when it came to traffic objects. The configuration loaded without any errors and our FW saw the GARP rom the self ip and caused issues with applications. I did not even do a save sys config. The VE F5s were in a HA state and has auto sync enabled, the configuration did sync as expected.

All virtual were showing as disabled but the logs showed the virtuals as becoming available, Enabled and then Disabled. It didn't make sense.

F5 is running 12.1.4.1 and I do see some oddities in the known issues around self ips overriding the virtual-address settings.

https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-bigip-12-1-4-1.html#A580303-5

How did they become available?

Anyone seen a GARP when loading a configuration in a disabled / no arp state?