I have set this as a blocker but I would not consider it a hard blocker. If a native android application becomes frozen then the user fixes that by manually closing and reopening the application. I am not sure its even helpful to provide an alternative way to do that, particularly when that alternative can conflict and be overridden by web content (pull to refresh is broken on twitter unless you know to do it in the header)

So yeh this may be added as something browser wide but we will not be doing a seperate implementation for pwa