I'm going to disagree with your last point because it should add the caveat that it makes sense when working with third party libraries. It makes sense to implement a wrapper with senseable defaults that comprises of +80% of use cases
I can agree with that wholeheartedly and admit to the practice myself...particularly with libs with a large surface area or which are used in many other places in the company.