Accessing Memory Optimised Tables Under Snapshot Isolation
If you intend to be able to update/insert through the view, it will likely not work. Please see my post here:
http://nedotter.com/archive/2017/07/dml-for-memory-optimized-tables-in-partitioned-views/
Rows cannot transition to/from the memory-optimzed side by changing the key/partitioning value. Depending on the version of SQL you are running, it will either cause a stack dump or give an error saying it's unsupported.
Though Microsoft has marketed memory-optimized tables as a hot/cold solution, it can't be done in most cases, at least not without tons of manual intervention. There is no way to validate a FK across the traditional/memory-optimized divide. See my post here:
http://nedotter.com/archive/2016/05/in-memory-oltp-relationship-status-its-complicated/
I've written a few posts on memory-optimized tables and isolation levels here:
http://nedotter.com/archive/2017/08/all-about-in-memory-isolation-levels-part-1/
http://nedotter.com/archive/2017/08/all-about-in-memory-isolation-levels-part-2/
Have you proven that the performance issues you are experiencing would be solved by In-Memory OLTP? The use cases are quite narrow.