ARM in itself is still old, you can not deny that.
Not as old as x86 - an instruction set which has roots going back to the 8008 in 1972 - 'easy translation' of 8008/8080 code was part of the brief for the 8086 in 1978, and since then
binary compatibility has been a thing. The original ARM is at least a decade younger and was designed from the ground up (with
inspiration from 6502 and Berkeley RISC but not compatibility - anyway, an ARM 2 could software-emulate a 6502 faster than the real thing...) - and from what I can glean quickly, binary compatibility with the original ISA (not the same as modern ARM32) is very limited and hasn't been a priority.
Will it interface to PCIe or some other bus? And, and how many total PCIe lanes available and how fast? Have been following ARM devices and they usually have limited or no PCIe.
Yes, ARM can do PCIe (e.g.
https://www.gigabyte.com/uk/Server-Motherboard/MP30-AR1-rev-11#ov) - it's just not in great demand on phones, tablets or cheap "maker" boards (like the Raspberry Pi) built from surplus set-top-box chipsets. Quite likely that the A12 has limited/no PCIe which may be why Apple can't just hang a Titan Ridge chip off it to get Thunderbolt. I'd guess that the "real" Apple Mac Silicon will have USB4/Thunderbolt 4 on-chip.
Bear in mind, though, that (a) only the Mac Pro has PCIe slots (and any Mac Pro/iMac Pro replacement is likely to be the last step of the 2 year transition), (b) it sounds like the first wave of ARM Macs are going to rely on Apple Silicon iGPUs and (c) the SSD controller is baked onto the Apple Silicon, so while the SSD may hang off something PCIe-like, those lines are going to be dedicated to Apple's proprietary SSDs. So it's not clear what PCIe would be 'for' in a MacBook or iMac - the real question there is whether the Thunderbolt/USB4 implementation will support eGPUs or PCIe enclosures.
Many audio interfaces have gone class-compliant which in theory should work with ARM Macs (they'll work with iPads and iPhones if they have their own power). The exceptions would be the UA Apollos and other audio I/Fs that require sophisticated control software.
"Class compliant" would already be on my "must have" list, given the annual opportunity for low-level drivers to be broken by the latest OS update. "Control software" doesn't have to be low-level - it could be implemented via a virtual MIDI interface, sending control voltages via audio channels, talking to an on-device webserver etc. Plenty of MIDI devices come with "control panel" software, but all that usually does is send CC and SysEx messages via the class-compliant MIDI interface - and should be perfectly fine under Rosetta. The real "big bang" here is the dropping of 32-bit support - which some people who have been holding off from Catalina are going to face at the same time as switching to ARM. Fortunately, I think Logic itself dropped 32-bit plug-in support some time ago.
Have to say, looking at the Apollo website, it's hard to see what is "drivers/control software" and what is just bundled audio effect plug-ins. Still - they have at least one USB version so they can get going on that with the dev kit

For actual audio plug-ins it is somewhat more likely that they'll have hand-optimised x86 code in them - but frankly the way forward there should be to replace all that with system calls and let the OS do the optimising (especially since Apple-proprietary on-chip acceleration is likely to be a 'thing' with future ARM chips). You can do that (and work through all the other checklists for ARM compatibility) on an x86. The mantra should really be "welcome to 2020 - make it CPU independent" not "make it ARM dependent".
...for anybody with low-level drivers that really do give one-ier '1s', rounder '0s' and (more realistically) better latency, then there's probably not a lot of point testing it on anything but Apple's final USB4/TB implementation.
As for software, stick with Logic Pro and you'll be fine for a DAW. If you use 3rd party plugins you'll likely have to wait.
True, but I should imagine that it is pretty common for Logic users to have spent several times more on third-party instruments and effects than they did on Logic itself...