No, AFAIK the only reason that view had different scrolling was because it was an overflowing div which had the -webkit-overflow-scroll: touch property to give it any momentum.
I worked on a website that experienced this same problem several years ago. The designers were pretty insistent on a design that would require the crappy non-native scrolling, but luckily management stepped in and said no to them.
Point being, UX should dictate design, not vice-versa. If you can't implement something the way you want without messing up something as important as scrolling then don't do it.
The irony here is that the two most important features of the web are arguably URLs and scrollable pages. And AMP screwed up both of them.
