my point is that most people don't have the opsec skills to outsmart big data. it doesn't matter if you coinjoin/whirlpool into thousands of outputs that go off and do different things. You can simplify the graph traversal by targeting the person at the start of KYC instead of trying to trace backward from the point of offense. You don't need to traverse back from a channel open request and get lost in a coinjoin if you are looking to target a specific human and find out what they've done, just start with the human, examine all of their KYC outputs to flatten out all the coinjoins to specific Lightning Node channel open operations. If you find that all (or even a significant number) of the channel opens are children of coinjoins that this user originated with KYC, you found your node operator. It doesn't matter if you have a thousand or a million shuffled operations. This can be examined in a few seconds of compute.

Patterns of spending are an opsec vulnerability and doing something like running a business or operating a routing node are going to create a trail.