I suppose there is not a clear answer for this. The default is definitely not better, since there are a few drivers that are best left out. However, I prefer to have extra work: I install all drivers, and then manually go to the drivers64UEFI and remove the ones I don't need. I place them in a backup folder, in case I discover that I need them after all. Others perhaps prefer to not install some drivers from the beginning. Remember to only use one of the AptioFix drivers, and to always select "Install for UEFI booting only".
I don't understand what you mean by "disk numbers in Clover". Does Clover use disk numbers somewhere?
I think you might be confusing something about APFS. I think "Disk Utility" has a very bad interface, and I prefer to use the command line diskutil:
An APFS partition is mounted as a whole virtual disk (it shows as "synthesized" in diskutil). But this virtual disk does not have the fat32 partition, that belongs to your real boot disk. And that fat32 partition, like you said, is the special one -- it has some special flags that mark it as ESP (EFI System Partition), where the UEFI looks for *.efi files to boot.
Here's my partition configuration:
Code:
$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.1 TB disk0
1: EFI ESP_SSD 536.9 MB disk0s1
2: Apple_HFS Local 930.0 GB disk0s2
3: Apple_APFS Container disk3 65.9 GB disk0s3
4: Microsoft Basic Data Data 53.5 GB disk0s4
/dev/disk1 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 250.1 GB disk1
1: EFI ESP_NVME 536.9 MB disk1s1
2: Microsoft Basic Data Win10 93.5 GB disk1s2
3: Windows Recovery 889.2 MB disk1s3
4: Apple_APFS Container disk2 104.9 GB disk1s4
5: Linux Filesystem 50.3 GB disk1s5
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +104.9 GB disk2
Physical Store disk1s4
1: APFS Volume macOS 45.2 GB disk2s1
2: APFS Volume Preboot 21.0 MB disk2s2
3: APFS Volume Recovery 515.1 MB disk2s3
4: APFS Volume VM 17.2 GB disk2s4
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +65.9 GB disk3
Physical Store disk0s3
1: APFS Volume Test 12.9 GB disk3s1
2: APFS Volume Preboot 21.3 MB disk3s2
3: APFS Volume Recovery 514.8 MB disk3s3
4: APFS Volume VM 17.2 GB disk3s4
I have 2 disks, disk0 and disk1.
Both have an ESP, in disk0s1 and disk1s1. This is not necessary, but I always keep one with an old Clover that I know is bootable, and install new stuff Clover and new configs in the other.
Then you'll see that disk0 has an APFS partition in disk0s3 and that disk1 has another in disk1s4.
Each APFS partition shows up has a virtual disk: disk0s3 is disk3 and disk1s4 is disk2. Finally, each of these virtual disks shows the partitions they have: disk3s1 and disk2s1. But since each of these partitions has a full macOS inside (I use disk2s1="macOS" as my normal boot partition and disk3s1="Test" as a test partition), each APFS virtual disk also has a Preboot and a Recovery partition.
But you see, the container (the APFS partition in the real disk) does not have the ESP.
after more than 2 days of uptime. So none of the changes I've made are relevant to fix the issue.
.. My choice would have been to e.g. directly build a system with a natively supported Vega. I chose the Nvidia to help all Nvidia freaks in their to be expected issues. The native implementation of the Vega just would have been trivial and the much better option 
