Sure, if you write a module / script for retrieving the budgets you can save a remarkable amount of time. One option is to retrieve the budgets via the budget histories. You can retrieve the histories anytime (e.g. during the simulation or after the simulation). In my point of view, this option is the most comfortable way, because you do not need to loop through mesh nodes to retrieve the budgets.
The FEFLOW Demo data provide a sample Python script which illustrates the workflow (getBudgetHistories.py):
https://www.mikepoweredbydhi.com/download/mike-2017/feflow-demo-data?ref=%7B48049242-9F00-48BE-82FA-7D0C1820F7A8%7D
Apart from retrieving the budget histories, the script also plots the histories as a png-file.
Please note, due to historical reasons the budget histories are available in single precision only.
Of course, alternative workflows for retrieving the budgets are also available. Please let me know if you do not like to use the histories.