This is not a solution because even without null move pruning stockfish needs many millions of nodes to get the right move in most of these positions.voyagerOne wrote:Maybe an idea is for SF to run a very quick search with null-move pruning disabled...then switch null-move pruning back on.
That way it won't miss these type of positions.
It may be better simply not to use null move pruning when the remaining depth is high(at least 20) and I remember that it does not change nothing at 1 minutes per game inspite of the fact that stockfish get clearly higher depths at that time control
but the stockfish team prefer not to do it because of an unbproved fear that it does not scale well when stockfish has null move verification code that also may cause it to be weaker at long time control that they do not remove.