It seems that on 32-bit ARM, the original reason for the lower limit has disappeared over time, and raising the stack limit there again to the same 984KB as on ia32/x64 might be worth a shot.
However, what Node/Debian cares about is arm64, and I see no reason to assume that anything has changed there since the limit was lowered. So I wouldn't be comfortable raising it.
Since (per
crbug.com/v8/10575) the issue was specific to WebView, maybe the best path forward would be for Node to float a patch. V8 itself doesn't know what product it's getting embedded into.
FWIW, there is no guarantee that the same stack size allows the same recursion depth on different platforms. In particular, 32-bit platforms will allow significantly higher recursion depths than 64-bit platforms per kilobyte of stack space, because most spilled values are register-sized. There could also be platform-specific differences between different 64-bit architectures, in particular in optimized code.
The "proper" fix is to design JS applications such that they don't even approach the stack limit. If 984 vs 864 makes a given app work or fail, then it's walking on very thin ice either way.