AFAIK, the two leading Mac acquisition solutions on the market today image Macs with the T2 chip to AFF4 or to a logical image such as a sparse image, or export the data to loose files. The sparse image is a bit more flexible as it can be mounted natively on a Mac without extra tools, but it is a logical image. The AFF4 image of a T2 Mac is more along the lines of a physical image, with some restrictions such as unallocated space being still encrypted (as of this writing).
What options you have depends largely on what tools you have access to. AFF4 support is currently very limited in most mainstream tools. X-Ways has APFS support and allows ingesting AFF4 images by using a third-party plugin from Evimetry. If you have X-Ways, you can download the plug-in here.
Something that might catch you by surprise is that when you point to an AFF4 image with the plug-in installed, X-Ways hangs for a minute or two with no progress indication. Presumably, the Evimetry plug-in is doing some background work there to present the AFF4 image in a way that X-Ways can work with. It would be great to have some progress indicator at that stage. I hope Schatz and Fleischmann can collaborate on building AFF4 support straight into X-Ways for a better user experience.
Also, Evimetry has a freely available file system bridge which loads the AFF4 image and presents it as a raw image. You can then ingest the raw image into an APFS-aware tool, or copy it out as a raw image for use by itself. You can get the file system bridge with freely available Evimetry Community.
Another logical option is to use BlackLight, which supports AFF4 and APFS. Working on Mac data on a Mac is generally a good idea due to the native support built into the OS.
If you need to add a new product to your workflow to support AFF4 & APFS, I would suggest looking into its search capabilities carefully to make sure they satisfy your requirements. For instance, OCRing documents without extractable text is a common requirement when performing blanket keyword searches, but many popular DFIR tools do not have this capability in their workflow. Also, if your search requires complex search expressions containing RegEx, proximity operators, etc, I would inquire about the search syntax of the tool to see what is possible.