Yup. Often providing payment perverts incentives too. forwarding txn is so damn cheap that lots of people will do it for 'free' (just the compensation of helping the network overall).... once you start paying people won't forward txn that have too many hops for them to get paid on anymore.
Another thing not discussed in the embodiment of the payment chain. Here is how it would have to work:
Today you construct SIGN_A(TX()) and that gets flooded. Under this system you'd have to instead construct SIGN_A(TX()+PEER_X) for each of your X peers. Then, peer B for example would construct SIGN_B(SIGN_A(TX()+PEER_B)+PEER_C) .. and C would construct SIGN_C(SIGN_B(SIGN_A(TX()+PEER_B)+PEER_C)+PEER_D) ... and so on. So each hop would now require $HOPS expensive signature validations, plus an expensive signing operation per next-hop peer, and would also add ~130 bytes of data (the next public key and a signature). Just two hops would easily more than double the computational and storage cost of the transaction.
It's a neat area of research, but I'm doubtful that its actually applicable to bitcoin.