Short version: CX handled my misconnection reasonably well. There's no ill-intended foulplay.

Long version:
I'm generally lucky when it comes to travelling (knocking on wood) and so I don't have much misconnection story to share. But this February I flew PEK-HKG-NRT, all on one ticket on CX in J, with 2+hours between each flight. Departure was delayed by about 1.5 hours at PEK due to MX right after push back. So misconnection was certain.

During the PEK-HKG flight I monitored my PNR like a hawk with inflight WiFi, and started searching for alternative arrangement. Later still during the first flight CX auto switched me to a red-eye HKG-NRT which would land about 10 hours behind original scheduled time of arrival at NRT. I spoke to ISM and requested him to relay to ground to switch to HKG-HND in that afternoon which should depart 2 hours after my touch down in HKG. ISM fully understood my requirements and assisted right away. He came back saying the HKG-HND was full in J , but could accommodate me in Y if I didn't mind. So I accepted it and ISM alerted ground for arrangement.

Right after landing at HKG a ground agent met me at arrival gate handing me my Y boarding pass. Then I went to the Bridge hoping to get a bulkhead/exit row seat in Y. Lounge dragon noted my ordeal from record without me saying it, and found a J seat on that HND flight for me. So eventually after all the saga I only arrived late by 1 hour but landing at HND was a silver lining. I lost a pre-ordered salmon main so to speak, if every loss must be accounted for.

So I want to say misconnection happens, and auto-protection was not ideal. But CX in my case was totally forthcoming in making up the issue, and eventually provided a satisfactory response after some back and forth. CX didn't want to spoil my trip intentionally and I see no reason why they would want to do so.