If a link is saturated, say via TCP, then UDP data can still get dropped AFAIK.
Searching I found this blog post[1] which takes a small stab at it. Would be interesting to try other setups with more data.
Regardless, using UDP one should always be prepared to handle dropped and out-of-order packets.
Nothing is perfect, so I'll keep using UDP on a switch and TCP on the internet.
If send a 1Gbit udp stream over a switch to another machine there will be no drops if both are connected with 1Gbit, the same is true if you use tcp, and over a router assuming its capable of forwarding that amount of traffic. If you have a third machine sending udp or tcp traffic towards the one receiving the 1Gbit udp stream you'll have drops on both streams. Doesn't matter what protocol you use, if you have congestion you'll have drops. You typically use udp if your application is real time, or if you want to create your own reliability mechanism and/or avoid issues with devices in the middle that does things with tcp.
However they can still occur, maybe due to some unexpected congestion or other issues. So long as your application can deal with that you should be good.
Like intermittent EMI causing bit flips and checksum failures, which happened to me once in an IoT application where the Ethernet cable to an outbuilding was buried next to the power line, and the network would die whenever the furnace kicked on.
Nice review by ServeTheHome here[2].
[1]: https://mikrotik.com/product/crs305_1g_4s_in
[2]: https://www.servethehome.com/mikrotik-crs305-1g-4sin-review-...
Edit: Apparently LGS105/LGS108 has 10Gb/s switching capacity allready so I'm good!