Eh, if you're going to go that route, then you'd want/need to take into account the whole bounty hunters sent out as part of the LEW quest. Since they can happen anywhere you're adventuring as well, etc, etc. I think the easier solution is to just not try to use the Temple if you know you're going to end up in fights...
The LEW quest bounty hunters seem to me to have a much broader scope than this, which is limited to the use of one familiar (and, once Mafia tracks them, only while you can still have fights). That said, I don’t think that paying attention to when bounty hunters are after you is something outside the scope of the script, although I don’t expect it to be implemented. More below.
As for not using it at the Temple, that sequence is one of the major draws of the Hipster: it’ll speed up your Hidden Temple because the fights can replace non-combats (i.e. good, free stats replace low-yield adventures) but not the quest superlikelies.
Though I suppose this doesn't have THAT many options yet on its Relay settings page... an "always use restoration levels" setting could be added that allows for ignoring the location, always returns need_only_1hp() as false, and can be set by the user whenever their status changes without needing to implement a lot of hacks to try to figure out current status, familiar, or other problematic feature.
I dunno, I don’t really see this as a hack, conceptually. In general, you only need 1 HP in the areas that the function checks for because you know you aren’t going to be meeting any enemies. If that changes—i.e. you know you might meet enemies—then shouldn’t you act accordingly? As regards bounty hunters, consider this: is it really safe to adventure with 1 HP during that 15 adventure window where one can appear? Is the feature outside the scope of the script or is it rather that implementing that feature in a robust fashion would be a pain in the neck (if not impossible)?
I would agree with what you’re saying if the script always blindly restored HP/MP, but it already
is context-aware simply through paying attention to your location. This is a simple change that would make it slightly more context-aware.