If the node has dropped the original transaction, it will accept the replacement.
If the node still has the original transaction, and has full RBF disabled, it will reject the replacement.
If the node still has the original transaction, and has full RBF enabled, it will accept the replacement, provided the replacement meets the fee criteria for RBF replacements.
Obviously, each node owner can decide for themselves whether or not they will support full RBF. But is there a way for a 3rd-party (like you or me) to know which node supports full RBF? It could help when you need to create such a doublespend transaction.
Even though the purging rate is 10 sat/vByte right now and OP only pays 7, Mempool.Space hasn't dropped his transaction. I am guessing many other nodes still have it in their memory even now. Knowing exactly where to go would speed things up.