I find your description somewhat unclear.

The only thing I have done which kind of fits your description is that I have written code with hooks that are available by subclassing, and then I exported a utility function which could be used to take a few desired callbacks and write your class for you. This worked well because providing hooks through subclassing was a natural implementation, but it was cumbersome to write lots of little subclasses that were all mainly the same, so I did away with the boilerplate.

Is that what you are talking about? If not then could you explain a little more verbosely, possibly with some code examples for how one would use your interface?