It isn't entirely clear how your UI is structured, but consider not using such unique indirect subexpressions.
Indirect bindings should always look like {1}/SomeSuffix, where {1} points at {view.params.tagpath}
Where you pass a tagpath from a view into a nested view, use an expression like concat({view.params.tagpath}, '/AnotherSuffix') so that the nested view gets a tagpath parameter already prepared for its own internal use.
Do you think using indirect addressing could put stress on the cpu? Ignition might not perform well. I noticed that some site takes forever to open, it takes long time to download resources to the local. When you click something, it takes a moment for the system to update the tag values, you can see the object turn from error to clear. I wish Ignition optimize performance.
That is almost always due to have a large number of resources in the project. Indirect binding is a way to re-use one resource in many places in your project, instead of creating many custom resources, reducing the startup time.
There are so many ways a developer can shoot their own foot when creating Ignition applications that I cannot list them. The ability to make Ignition do almost anything imaginable comes with the possibility of poor implementations. Consider sharing your troublesome projects here for advice in detail.