Do you realize these chips have a limited range of hardware functions that can be attached to each pin? Many Arduinos and
Arduino compatibles use pins 10..13 as the SPI bus so that limits the use LED pin already - you can't use it if using SPI on
many boards.
In attempting to be Arduino-compatible and pinning out useful busses on the available pins compromizes have to be made - very
few microcontrollers have fully multiplexed I/O connections, and different microcontrollers are different, often very different - different
Teensy's for example use completely different chips, yet present as similar a pinout as possible. For instance the T3.2 uses the
MK20DX256 from Freescale, but the T4's use the iMXRT1062 from NXP - there are enough differences between these to force a different
audio board version to be designed for the T4 - that's just how it is...
My advice is learn the lesson that one has to check shield pinouts for clashes, in fact there's several ways hardware can clash,
either pin use, interrupts, timer and other resource usage --- hardware is not as flexible as software, you can't just redefine it,
you have to work with what you've got, and its a good idea before launching into a project to list all the pins and resources and
check for clashes. This is both for hardware and for libraries that directly interface to hardware.