Speaking of Intelligent Query Processing, does it have a functional dependency on Query Store?
One of my PMP goals for 2019 is to implement Query Store on all of our >= v2016 instances. However, an annoying limitation of Query Store, something I wish the SQL Server team would have addressed in v2017 or the upcoming v2019, is that QS doesn't work on AlwaysOn read-only replicas. What I mean is that QS is there, but it's disabled. So, if you look at QS on a secondary, what you're really seeing is replicated from the primary, which can be confusing until you realize what's going on. I know the limitation is because QS is enabled at the database level, and QS system tables are contained inside the database, but a sensible solution would be to support a centralized instance level QS database.
Actually, it's the read-only replicas where I could leverage Query Store the most, because that's what receives the largest volume of application queries. The primary is only used for ETL, and I have other options for monitoring that.
We're starting to see cool new features and tools built on top of Query Store, so let's get it working when and where it's needed.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho