The issue started happens with huge project, when I try to use VS2022. Everything is fine in VS2017. Here is the narrowed use case

Picture that you have projectA, referenced for projectB.

At some point something happens with projectA references and projectA.CopyCompleted file is updated.
Now, we're starting build and VS2022 detects reference was changed:

FastUpToDate: Input marker 'projectA.csproj.CopyComplete' is newer (2022-10-07 23:12:43.795) than output marker projectB.csproj.CopyComplete' (2022-10-07 20:48:54.311), not up-to-date. (projectB)

ProjectB is starting to build, but projectA dependencies were already updated before (let's don't discuss how and why).
But since dependencies were not copied, projectB.csproj.CopyComplete file is not changed:

Task "Touch" skipped, due to false condition; ('@(ReferencesCopiedInThisBuild)' != '' and '$(WroteAtLeastOneFile)' == 'true') was evaluated as ('my binaries here.dll;...' != '' and 'False' == 'true').

Now, I start build again, VS2022 again detects projectA.csproj.CopyComplete' is newer and rebuild projectB again and again

I tried update VS2022 to latest version (17.3.5), but the issue is still there.
I made workaround to create target after "CompileDependsOn" and explicitly touch 'projectB.csproj.CopyComplete' file with projectB (_AssemblyTimestampAfterCompile) time, but obviously I don't like this workaround.