any way to create such function would mean to create documentation for each function anyway... so why not simply build documentation on what already exists on vB?!...
Yes, documentation would be required, but it would be straightforward, since the entire idea is that the interfaces would be very straightforward.
Maintaining a handful of pages for documentation is likely outweighed by the benefits of a standard hacking toolkit:
1) Easier to implement common hack features.
2) Isolate hacks, to some extent, from changes in vB releases. All one needs to do is upload new vbExtension.php if incompatible changes are introduced.
3) Less bugs since everyone is not coding common tasks by hand.