Sorry for using the term "dumbed down" rather than "simplified for new users", I suppose that sounds better. I would log bugs and patches if I understood the process. I've been using PfSense for about 5 months now so I'm a relatively new user.
On this issue I initially suggested that all native unbound commands be recognized by the GUI custom entry box such that they override the GUI setttings. Or if this is unacceptable, at least allow custom commands that are not configurable via the GUI. I could test every unbound command to see if it keeps the service from starting but that would take about a day. I'm sure someone more familiar could generate a list in a few minutes.
The bigger question is, "what's the goal"? What can and can't be done with the unbound package script. So far I'm seeing more interest in using command parameters to generate other command parameters. In other words, a continuation to keep it simple and automated, rather than improving the ability to troubleshoot performance issues should they arise. Maybe you can explain why the native commands weren't included in the package. Is it just the time and effort to provide features that may get little use?
As someone who had been using a stand-alone unbound service with only a script, surely you would expect some moaning when most of the script settings were rejected by PfSense. It would have been nice to drop in a well tested and stable script rather than use the automated package that restarts now and then. I may go back to a stand-alone service if I can't resolve the restarts.
Are there other 64-bit users seeing their unbound package perform unattended restarts? No idea how to troubleshoot this especially with many of the commands unrecognized. Fortunately the service restarts fairly quick so it doesn't seem to cause much disruption. However with each occurance the cache is cleared and has to begin rebuilding when the service starts making the package less effective. I don't save the cache because of the SSD and it adds too much time to a PfSense reboot.