There is no limitation that restricts the V2 abi to little endian machines. Rather then checking based on endianess we should be gating behavior based on abi flags.
This cleans up most of the existing checks, but unfortunately the PPC64 target constructor has one such endianess check that comes before we have processed the e_flags and don't know the abi version yet. Since we are working on a patch to remove the remaining V1 abi specific code I've left that check as is for now.
IMO this is going to get unwieldy after a while (making it part of the base class), but it looks like you're also just following existing practice.