Cakewalk tech support advised me against those
So presumably they have had some frustrated users calling.
This compatibility issue is one of the more important reasons not to commit to an interface that plugs directly into the motherboard. To engineer an interface to an external standard communication protocol you only need to deliver the data in the correct format and signal specifications to a plug of the right configuration. To make something work inside a computer of the future, you need to have enough space to fit it, the right power supply etc., AND you have to figure out what socket will be there before anyone has invented it, or some way to fit an adapter inside the case and drivers that will translate everything so that the legacy equipment sees it as if it were still plugged in to an obsolete motherboard. There are plenty of usable PCIe to USB and firewire adapters available, even though much of the external equipment that is connected to them was built during the PCIold era, and a pretty good bet that if PCIe is replaced, someone can engineer a new adapter to fit the new MB socket and put out USB or firewire data that will keep the external device happy. The tiny improvement in theorectical decreased latency by direct-to-motherboard audio interface connection is probably not worth the cost of trashing an audio interface that cost a couple of grand because some hot new MB socket has become popular.