The use-case that you presented was hiding controls and clearing the values in them.
The computed trigger is recommended as this considers all the data that could affect whether Field3 and Field 4 should be filled or cleared. This also means that the dependency can be triggered after a single calculation is completed.
The solution that you used in 2023.06 relies on a chain of dependencies. This meant that the Form Engine needed to iterate through your dependencies in the correct order to reach the correct result that you are looking for. This can lead to long chains which can then cause poor performance. An example of where this can be found in Performance issue in form with many repeat entries.
By following the recommendations that I made above and also migrating to 2024.06 significant performance improvements can be made, partly because the Form Engine no-longer iterates through your models in the same way.
I hope you also notice the performance benefits after migration.
An alternative if you only need to hide the fields would be to model a Dependent Control. Please note, that the Control and Element to be hidden need to be on the same screen.