Allow me to clarify: the defaults are gibberish that looks arbitrarily random enough to be confusing to some people (YT included!)
What if you update the BIOS, swap a NIC around to another slot, change PCIe lanes, add a hardware telephony card – while there’s still time, buy more Sangoma T1 cards ASAP! 
– etc. ?
Maybe then you might agree that there is some chance that all the NICs get renamed because now there is something else different that the BIOS is reporting in at the previous “slot”, or, potentially, oops your PBX is now answering DHCP requests from your customer’s PCs because something higher up the stack decided to stick with the capriciously-assigned enp0s3 name instead of a more reasonable choice like pbxeth0 and your other config files all need a touch now because you didn’t move the cables around correctly (which gets to the question of correctness w/r/t how the BIOS is doing its thing that appears at minimum potentially undocumented magicrandomness) ?
Potentially, some day, sure! For now, you can hand edit one file when necessary: /etc/network/interfaces.d/pbx-renames. Although just by that file existing with the ISO (or a similar file via whatever you do non-ISO) and providing a lock of sane-names-to-MACs makes your network setup relatively impervious to BIOS-inflicted “slot” changes (unless maybe you are overwriting MACs in the BIOS 
…)
That particular code comment is a description of the after state not the before state because network names assigned by kernel/udev/systemd are NOT sticky based on MAC but on the “bus” and “slot” as you so eloquently described earlier in your post comment (lack of mention of BIOS activity in said comment was noted.)
Any system with several NICs like enp0s3, enp1s2, and enp4s0 is much less pleasant to look at compared to pbxeth0, pbxeth1, and pbxeth2 – doubly-so if the stickers on the box right above the Ethernet ports are printed with little words like LAN0, LAN1 and LAN2 (as the Sangoma appliances are.)