I do miss the extra functionality being provided by that wrapper. If it is about a tuple representation of the version, that could be provided on the SDL_version class level rather than adding a new function for it.
That was my original thought too, but I couldn't think of immediate solution how to make ctypes.Structure object also a tuple. It seems that you need methods both from Structure and tuple and I am not sure they won't overlap and that mixin with two parents is actually a safe choice for ctypes.
Another reasons is that I like that SDL_* is 1:1 mapped to SDL2 API. I am afraid adding new user visible methods, because it will break the mapping (I like to think that I'll be able to port some critical parts of my Python prototype to C when performance will be an issue).