I'm just asking because I have no idea: Would a change from 16-bit to 24 or 32-bit be a huge upheaval? Would it be impossible to do without dropping support for 16-bit players? Technical query, not a feature request!
At minimum, we'd need to make the audio path variable-width at compile time, so 16-bit only devices don't incur any performance penalty.
A basic question is if we want to unconditionally use 24/32-bit audio on platform that support it, or switch back and forth at runtime. Switching makes everything a lot more complicated, with multiple code paths and new APIs.
Meanwhile. Our DSP/EQ/effect engine doesn't support >16bit. Additionally, we'd have to implement 16-24bit conversion for the various codecs/plugins that don't support >16bit audio (that said some of our targets only support 24/32-bit audio so that's already implemented, just not in a generic manner)