That is a really bad idea from a security standpoint.
Giving write access to any Nginx file from the application layer sounds very risky too. A slightly better approach would be to create a group that both nginx and www-data belong to, change the group ownership of the relevant files/directories to that group, and add group write permissions. That's still risky since an RCE anywhere in the program would makes those files writable for the attacker.
It's hard to say what the correct and safe approach would be without knowing the problem that you're trying to solve. Can you elaborate on that?
You could also allow www-data to run a specific script as nginx via the sudoers file:
www-data ALL=(nginx) NOPASSWD: /opt/my/script.sh
You could then invoke that script from Laravel. But like I said, I'd need to know the actual problem.