Seems the developers are aware of this issue. Seems to me they are not so interested in fixing it as they dont see this problem on thier own OS! I would (if I were you) post a follow up reply in that issue stating you too are having the issue - just to let the developer know the issue still exists & is probably affecting more people than they realise (they may not be aware of how common this is as people tend not to bother reporting issues and generate workarounds - much like yourself)
In the mean time, there are several threads on this forum related to restarting node-red
this one MIGHT work for you (it restarts your flows via the API - import the last flow under "solution 2" in that link)
