Not sure if this idea conflicts with the commercial support model or is practical at all.

There will always be some common tasks that are too specific or seldom necessary to be implemented in the WebUI or as official part of the product.
Such tasks could be encapsulated in something like mini-tools (source code, shell-/sql-scripts, etc.) and be provided together with the source code in a dedicated directory which will not be part of a regular installation.

Example use case for such a mini-tool:
SLA calculation is initiated on event processing what prevents historical data to be taken into account. Interpreting historical data generally or on SLA modification is inefficient and would lead to performance issues.
But the same methods used in event processing could be put into a separate binary for manual usage and be fed based on historical data. This program could then be used for the rare but likely cases when needed.