kern.wxabort was added as a mechanism to assist developers at figuring
why programs do W|X allocations, deep inside.

This creates nice coredumps, sometimes stored to avoid privsep/chroot
issues using kern.nosuidcoredump=3

Then, the developer can try to fix the program, or give up and use USE_WXNEEDED

I'm not sure we can ever consider this a normal-but-optional runtime
behaviour. By it's nature, it is silently unrecoverable.  I'm pretty
certain that making it a default is never going to be acceptable.