Apple did not supply EFI mode Window drivers for your Mac. Therefore, there is no point pursuing an EFI install of Windows. In the later versions of macOS (including High Sierra), the Boot Camp Assistant can be used to download the Windows Support Software for 64 bit installs of Windows on your Mac. At the time of this writing, this download should be the same as downloading Boot Camp Support Software 5.1.5621.
Editing Bootcamp's Info.plist as solution is a myth. What you end up with is a installer for a different Mac. In other words, the installer usually will not even boot on the Mac used to create it.
Triple booting from your primary internal disk is not only possible, but has been documented at Ask Different, Super User and Ask Ubuntu. Of course, you have not specified which operating systems you wish include in your desired triple boot. For your Mac, the best course is to boot any Windows operating systems in legacy BIOS mode and all others in EFI mode.
The rEFInd boot manager is useful tool, but is usually not required to boot an operating system on newer Mac computers. The Apple Boot Manager usually is capable of booting any Mac compatible operating system, provided the operating system is installed in a way compatible with the Apple Boot Manager. For some operating systems, this may require you to modify some boot files' location and name after installation. On the other hand, rEFInd can often be used to avoid these types of modifications.
While GPT disks can have more than 4 partitions, the legacy mode BIOS booting of Windows allows only 4 partitions to be visible to Windows. Although, making more than 4 partitions visible to Windows is theoretically possible, I do not know of anyone every trying to do so. Also, there is no requirement that the first 4 GPT partitions be the ones visible to Windows.
I can provide the current disk configuration from a 2007 iMac as an example of a Mac computer with more than two operating systems installed. Below is the output from diskutil list.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Microsoft Basic Data Shark 202.0 GB disk0s2
3: Microsoft Basic Data Shark2 202.0 GB disk0s3
4: Microsoft Basic Data SHARK3 50.0 GB disk0s4
5: Apple_HFS Steelhead 245.1 GB disk0s5
6: Apple_Boot Recovery HD 650.0 MB disk0s6
7: Apple_HFS Ubuntu 199.2 MB disk0s7
8: Linux Swap 4.3 GB disk0s8
9: Linux Filesystem 93.9 GB disk0s9
10: Apple_HFS Steelhead2 198.9 GB disk0s10
11: Apple_Boot Recovery HD 650.0 MB disk0s11
12: EFI REFIND 134.2 MB disk0s12
This Mac has the following bootable partitions which can be selected from the Startup Manager.
Shark which has a BIOS bootable version of 64 bit Windows 10 installed. Windows is aware of the EFI partition by can not access the partition. Windows does have access to the Shark (NTFS), Shark2 (NTFS) and SHARK3 (FAT32) partitions. Note: Occasionally, I have had a dual legacy BIOS boot of Windows using both Stark and Shark2, but currently this is not the case. Steelhead which has Yosemite installed.Recovery HD (immediately after Steelhead) which is the Yosemite recovery partition.Ubuntu which has rEFInd installed. The boot manager rEFInd is configured to silently boot the Ubuntu operation system. This is an older version of Ubuntu which requires either a modification of the installation or the use of rEFInd in order to boot on Mac computers. I believe the current version of Ubuntu no longer requires any modifications or the use of rEFInd.Steelhead2 which has El Capitan installed.Recovery HD (immediately after Steelhead2) which is the El Capitan recovery partition.REFIND which has rEFInd installed. This version of rEFInd is configure to allow the selection of the same boot options as the Startup Manager (which the exception of itself).
Best Answer
Trying to get a "more recent Mac's bootcamp installer" is the wrong approach to take in a effort to solve your problem. Especially, since there are other ways to solve your problem which involve using the rEFInd Boot Manager. This free software is capable of instructing the firmware to boot Mojave.
One solution involves creating a small 300 MB "Mac OS Extended (Journaled)" volume where rEFInd is installed. Here, rEFInd is configured to appear as a legacy OS X operating system. The Boot Camp software installed in your Windows operation system will detected this volume as OS X. When booting from this volume, rEFInd will automatically instruct the firmware to reboot to Mojave. This is setup to happen silently.
An example of how to setup rEFInd as described is given as the accepted answer to the question: macOS partition disappered after installing windows 10 using bootcamp.