The problem is more general than this.
Software packages (and not just SciKit - pretty much any package) do not provide tools just because they are useful and do not (in my experience) remove them because they are not useful. Tools get put into packages (and not removed) because:
People want them. People ask for them. For commercial packages, meeting customer demand is part of making money. For free packages, it's still part of "making customers happy". People really want automatic methods for variable selection and many of them don't want to listen to the reasons this is bad.
People want to write the code. The people who do the coding may not know the extent of problems with the method. Or the code may have been written before the problems were discovered.
Removing code is problematic. If a person updates software and it then makes previous programs return errors, that person is likely to be very unhappy, regardless of whether the error is, really, a good thing.
Now, as to your precise question -- do these selection methods have any value -- well, maybe. For one thing, they can let you replicate earlier research. For another, well, in a similar context I read someone's reply (I forget who -- it might have been Ripley, but I'm not sure)
The only reason to do this is to demonstrate how wrong it is.
So, you could use a "select best" function to show that select best functions don't work very well.