It really depends on how complex you want it to be. You can always take it a step further, but is it really worth it? That's something you need to consider.
In any case, regarding improvements to your current system: I believe the API doesn't offer webhooks and you have no control over that, but you do have full control over the Node service and your backend. I assume there's currently a scheduled command that checks Redis for changes. Instead of polling, you could notify your backend, using internal webhooks, pub/sub, or similar, whenever the data actually changes.
But again, is it really worth it? Added complexity comes at a cost, and you are probably better off keeping things simple until you truly need the upgrade.
That said, we have done something similar in the past, and I would keep it even simpler by consolidating everything into the same Laravel app. I dont see a need for a separate Node service unless its a business requirement. You could just run a background command as a daemon (similar to how Reverb works), and in case of changes broadcast an event to your frontend.