We have this idea in mind, and we have a GitHub issue for that, which you can upvote to express your interest.
There will be performance implications and also increased risk of exposing sensitive data, which is part of the reason we are not decided on that yet.
Plugins are normally a way for supporting new libraries/infrastructures, and less for monitoring custom data. Using a plugin that we don't maintain would expose you to frequent breaks due to dependency on internal APIs. The way to go with custom data is using our public APIs. Those are very stable and you can get a very long way with them.
Again- better not add your code to the plugin, but find a way around it with the public APIs. For example, you can create a span in your DAO code (if you use such) where you can store SQL with parameters (in which case you actually may want to look into our plugin to see what we do to reduce related performance costs). Adding to the plugin may yield the best results, but you will take the risk of having to maintain more frequently.