Yes, I believe in PXE/HTTP UEFI boot as the most flexible way of provisioning and this is our main goal. We do have many other workflows but booting from network will always be well tested and with most features.
You need at least a TFTP proxy there, you can even deploy it somewhere else, all you need is a working NFS mount to a TFTP server (of any kind), if deploying smart proxy “somewhere” is a big deal for you.
Indeed, it’s a little monster of ours 
You might find this handy:
https://docs.theforeman.org/nightly/Provisioning_Guide/index-foreman-el.html
Foreman currently supports manual IP, DB IPAM (Foreman owns the pool of IP addresses, just a single heap per subnet), DHCP mode (meaning DHCP proxy will find the next available IP from a range sequentially) and External IPAM which is an experimental feature - there is a plugin that integrates with MyIPAM and one more provider. This is fairly fresh code: