Duplicate network interfaces appearing after booting a mac2.metal instance from an ami image taken from mac2.metal instance

We are trying to build an ami for mac instances and we've observed a weird nuance - when booting a mac2.metal instance, performing some provisioning and then stopping and taking an ami image, the next mac2.metal instance has an extra "Thunderbolt Ethernet Slot 0" adapter, and each new ami image creation adds another one. For example, after 4/5 iterations of ami image creation -> then launching an instance from it -> then creating a new image yields 5 "Thunderbolt Ethernet Slot 0" adapters.

Here is the relevant cli tool output:

networksetup -listallhardwareports           

Hardware Port: Ethernet
Device: en0
Ethernet Address: 14:98:77:65:dd:4e

Hardware Port: Thunderbolt Ethernet Slot 0
Device: en14
Ethernet Address: 02:31:37:03:98:db

Hardware Port: Ethernet Adapter (en7)
Device: en7
Ethernet Address: 9a:67:dc:0f:f3:88

Hardware Port: Ethernet Adapter (en8)
Device: en8
Ethernet Address: 9a:67:dc:0f:f3:89

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: 36:3e:38:33:75:c0

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: 14:98:77:6e:9d:27

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: 36:3e:38:33:75:c0

Hardware Port: Thunderbolt 2
Device: en3
Ethernet Address: 36:3e:38:33:75:c4

VLAN Configurations

networksetup -listallnetworkservices         
An asterisk (*) denotes that a network service is disabled.
*Ethernet
Thunderbolt Ethernet Slot 0
Thunderbolt Ethernet Slot 0 2
Thunderbolt Ethernet Slot 0 3
Thunderbolt Ethernet Slot 0 4
Thunderbolt Ethernet Slot 0 5
Thunderbolt Bridge
Wi-Fi

ifconfig -a  
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 9a:67:dc:0f:f3:a9 
	inet6 fe80::9867:dcff:fe0f:f3a9%anpi1 prefixlen 64 scopeid 0x4 
	nd6 options=201<PERFORMNUD,DAD>
	media: none
	status: inactive
anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 9a:67:dc:0f:f3:a8 
	inet6 fe80::9867:dcff:fe0f:f3a8%anpi0 prefixlen 64 scopeid 0x5 
	nd6 options=201<PERFORMNUD,DAD>
	media: none
	status: inactive
en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
	ether 14:98:77:65:dd:4e 
	media: autoselect (none)
	status: inactive
en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 9a:67:dc:0f:f3:88 
	nd6 options=201<PERFORMNUD,DAD>
	media: none
	status: inactive
en8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 9a:67:dc:0f:f3:89 
	nd6 options=201<PERFORMNUD,DAD>
	media: none
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 36:3e:38:33:75:c0 
	media: autoselect <full-duplex>
	status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 36:3e:38:33:75:c4 
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 36:3e:38:33:75:c0 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 9 priority 0 path cost 0
	member: en3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 10 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
en14: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 9001
	options=6463<RXCSUM,TXCSUM,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 02:31:37:03:98:db 
	inet6  prefixlen 64 secured scopeid 0xc 
	inet  netmask 0xfffff000 broadcast 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (none)
	status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::c408:4771:32d0:886f%utun0 prefixlen 64 scopeid 0xd 
	nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::b113:6e1c:a65f:b1a7%utun1 prefixlen 64 scopeid 0xe 
	nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
	inet6 fe80::ce81:b1c:bd2c:69e%utun2 prefixlen 64 scopeid 0xf 
	nd6 options=201<PERFORMNUD,DAD>

As can be seen the extra adapters only show up in the gui and via networksetup -listallnetworkservices, but not in ifconfig or networksetup -listallhardwareports.

Is this a known expected behaviour and if yes, what can be done to avoid it and only have a single adapter?