For an overview, please check the Mobility Contoller VRD chapter 3.
The info below is just for ArubaOS 6.x (on 8.x licenses are centralized on the mobility master)
The master controller needs to have one license of all to enable the configuration of the features. So, master controller will need PEFV as well:
I believe that in order to use the master controller to redirect the APs to the right local, you might need an AP license as well.
Then with central licensing: all licenses (except controller bound licenses like PEFV/Via) are contributed to a central pool. So it does not really matter on which controller you install licenses, master or any of the locals. For management purposes, most customers opt to install just on the master controller. The benefit of centralized license (and part of your question) is that because the PEFNG/RFProtect are not consumed till APs actually terminate on the master (not recommended), the license just sits there and allows roles (PEFNG) and RFProtect and other config to be done on the master and distributed to the locals.
So for non-centralized, the table above applies, for centralized, you don't need additional licenses as because they are in the pool and as long no APs terminate on the master you have access to the commands and will be fine.
The PEFV is the big exception in this story as that license needs to be installed on both the master and optional backup-master to allow VIA configuration, and on the locals to terminate VIA clients and allow roles to be applied on the client traffic.
Note that this PEFV exception has changed in ArubaOS 8.x. That version no longer requires the license for the Mobility Master.
As you are posting in the training/certification section, I would follow the information in the VRD posted above, with the addition of the centralized licensing concept that is described above.
For production/design, please go ArubaOS 8.x to avoid these kinds of questions.