The thread specifically for a tool can't really be necroed unless the tool is well and truly dead. The ideal case for no activity would be a tool that worked so well there was no reason for any discussions at all...
All my interaction with DF apart from a limited site presence remains on hold until keyboard support has been restored, as I don't find a mouse only (or even mostly) game playable and thus don't have any interest in working on tools for it.
Thus, my current intention is to return to DF when keyboard support has been restored, but there's probably a limit to how many years I can wait before losing interest completely (it's been 1½ years since the announcement of the removal of keyboard support and the subsequent announcement of the reversal of that decision).
However, the UI changes will make an update a rather extensive task, and I have no idea how much work it would be replace the current overlay with a new one, or even if there would be suitable tiles available for it.
It can also be noted that the logic for biome determination is no longer correct, as DF changed some time before the Premium release (the ocean type boundaries have shifted a fair bit, while other differences are lesser). The DFHack plugin that performs this logic has not been updated (it would probably require a new disassembly effort to do so). If I remember correctly this script uses the Lua version of that code (written before the DFHack plugin exported the logic from the disassembly), but an update should probably hook into the DFHack plugin to improve future proofing.
It can also be noted that other things probably have changed, so research and usage of new/changed data structures would probably be required.
The most important keyboard support restoration would be the restoration of the Help key binding, as all my scripts have help screens using this key, and without this they won't work at all (The Librarian was updated on request, but I just disabled the help functionality entirely to get around that issue).
The Region Manipulator faces the same type of challenges as this script does.
I have no issues with someone else taking whatever logic they find useful in my scripts and roll their own, although I would prefer if they didn't use the same names for their scripts, as that would cause confusion.