If Nsight Compute is showing bank conflicts in the Memory Workload Analysis tables, there are truly conflicts in your kernel. The Source page metrics you referred can help in identifying the source of such conflicts, but they are not guaranteed to show all of them (i.e. there is no strict correlation in both directions).
You can find more info related to bank conflict analysis in Nsight Compute in this thread: Shared memory bank conflicts and nsight metric. Note that the “Memory L1 (Ideal) Transactions Shared” have since been renamed to “L1 Wavefronts Shared (Ideal)” in newer versions of the tool. Also, as hinted to in this reply, we are looking to make it easier to determine the source of any bank conflicts in future versions of the tool.