How do I use SQL Server's "Hekaton"? The SQL Server 2017 version on Linux comes packaged with a utility called mtlogreader.exe that is absent from the Windows distribution,

MtLog Reader - Dump Hekaton MtLog files

Usage: \\VBOXSVR\mssql\lib\sqlservr\Content\binn\mtlogreader.exe &lt;file&gt; [options]

Options:

        -verbose &lt;int&gt;  Verbosity (0-4) Default 1. (short form: -v)
        -buffio &lt;bool&gt;  Buffer stdout (true/false) Default true (short form: -b)
        -keySecret1 &lt;string&gt;    The first secret key blob used for crypto keys (short form: -k1)
        -keySecret2 &lt;string&gt;    The Second secret key blob used for crypto keys (short form: -k2)
        -instructionFile        Treat file as instructionfile. (short form: -i)
        -targetruntimeinseconds &lt;int&gt;   The target run time in seconds (only valid with -i). (short form: -t)
        -skipchksum     Skip checksum validation. (short form: -sc)
        -maxbsn &lt;uint64&gt;        Max BSN to dump. Default 0 (dump whole file). (short form: -m)

&lt;file&gt; has a different meaning depending on whether -instructionFile is specified
if -instructionFile is specified, &lt;file&gt; is a file containing checkpoint file
information extracted at dump time, containing the root file name followed by a
list of container directories (one per line).
 the -t parameter is an indication of how long to run the tool
when used with -i it is used to limit the processing of checkpoint files


I can't find much about Hekaton though. I've found some errors here and I see it has a pretty old wiki page where can I find documentation on the Hekaton subsystem but how to use it? Has Hekaton been rolled into the "Analysis Services"?
Hekaton was the internal Microsoft project that references the In-Memory OLTP feature, starting with SQL 2014. Some people still use the word Hekaton generically, to describe the In-Memory feature in any version of SQL server (2014, 2016, 2017). 

In-Memory OLTP is a feature that stands alone - it is not part of any other feature, i.e. Analysis Services. 

There is tons of info out there on the web about In-Memory OLTP, but I would caution you to avoid anything that references SQL 2014 (as you have above), because that was essentially v1.0, and much has changed since then. 

First - have you proven through a valid POC that your workload is likely to benefit from using In-Memory OLTP? 

I have blogged extensively about In-Memory OLTP, but you might be better off starting with the documentation, here:

https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization