See 2.5.6 here https://developer.apple.com/app-store/review/guidelines/
"2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript."
As for why this is, one can only speculate. There used to be an extremely strict "no interpreted code allowed", which was relaxed to "no interpreted downloaded code", which I think (with the addition of the JavaScriptCore framework and the lack of bans on bundling a LUA interpreter as many games do) has turned into a "no major functionality changes or additions in downloadable code". I guess their main concern was developers publishing app updates outside of the app store review team's oversight.
Besides that, both Firefox and Chrome on OS X are notorious for power usage issues. There's a very good likelyhood that'd be true under iOS as well and the last thing Apple wants is a bunch of users blaming their iDevices for poor battery performance when the issue is actually web engines that are bad at rationing energy.
You're right about power usage though. Even if they did allow third party engines, they wouldn't allow third party JIT compilers (much bigger attack surface, W|X memory protection is gated behind an apple-only entitlement) so those browsers would be second class citizens battery- and performance-wise for sure.