Actually not at all. AMP is specifically designed with HTTP/2 in mind and takes full advantage of it. E.g. it loads articles, scripts, images, fonts, etc. through a single HTTP 2 tunnel.
Can you elaborate? From what I can tell, AMP makes use of on-demand resource loading, which HTTP/2 prefers over bundled resources thanks to multiplexing.
From what I understood, there are a few contradictions like splitting up assets (preferable in HTTP/2) as opposed to concatenating/merging them (preferable in AMP). Perhaps I misunderstood
AMP encourages you to keep your assets separated, so you only load the bits you need. If a page is going to use <amp-youtube> you'll have to include the appropriate script tag for that component in the page, for example.