I don't follow. If you know what's wrong, then you're not confused, you're the opposite: you accurately know the situation. Confusion is if you think the automation setup will result in something different than what it's actually resulting in. And it can come in 2 flavors: first, not even knowing anything is wrong and merrily blundering toward CFIT; and second, knowing something is wrong but not understanding exactly what or why, and usually accompanied by an attempt to fix by frantically pushing buttons and twisting knobs.
Again no! I have said it before with AP on or off pilot's scan remains same only difference is with AP on, the AP makes changes and in manual pilot makes changes. With or without AP It's the loss of scan that causes the problem. Mode or no mode, right or wrong mode, you simply cannot make an approch without a periodic glance at the speed. In the cases we are discussing the crew never even expressed a surprise or utter a word regarding falling speed because they never looked at the speed and worse not even the mode. They assumed a mode that wasn't there, they assumed a speed that wasn't being maintained. In both the cases even the go around was not because they noticed speed or the ROD but because they were not reaching the runway otherwise they would have executed a 3 or 4G Landing. In case of Indian airlines they lost their lives because they were nine seconds too late. The engines were spooling up. Somebody needs maintain the parameters either the AP does it, the mode does it or the pilot does it. Nobody is not acceptable.