Regarding 0x415 - looks like in m case it's the same as you mean - 16bits are formed from byte0 and byte1.
Yeah it will give a lower resolution result when you shift the value instead of using the 2 bytes of data, but it's not a big issue if you don't need high resolution values.
However, I mainly wanted to point this out since you described "saw-like" data. The "saw-like' data is a counter and normally indicated you're looking at incomplete data.
Do you have any reference or guidelines about file format for Racechrono? If there's no much coding, may be worth to try it...
The rcz file format? No, but I haven't messed with racechrono as a data logger much since all the options have fairly slow polling. The app creator (aol of RaceChrono on forums), is really responsive on his forums by the way.
As for .dbc files, you can open them as text, but using a database editor like savvycan (picture I posted), makes the info much easier to digest. They are written in terms of bit position, not bytes, but it's not hard to convert the info into something racechono likes. I never found a good interface for logging CAN data with racechrono.
I watched Forscan traffic - it requests throttle/MAF/sparks timing explicitly on 0x78E, so it's possible to use the same approach.
I think you mean 0x7E8 or physical request/responses (7E0 -> 7E8), which racechrono considers OBDII headers I think. This data is extremely slow if you are looking at multiple PIDs. As for torque, what specifically are you looking for? Throttle position is essentially a torque request based on how the tables are tuned, engine state, TC, esc, etc. It sounds like all you're looking for is a 0x23 (read memory by address) value. There are quite a few different torque values though (desired torque, scheduled, etc indicated torque, engine brake torque, etc.) I can log it using hptuners and sniff the data if you need that info.
With all that being said, I meant a way to passively sniff things like spark, knock, stft, ltft, etc. I know how to pull all the data I need from either CAN IDs or OBD PIDs, but I haven't found a cheap solution for consolidating and viewing the data. I've never been able to get my MX+ to read CAN data in RaceChrono. I'm not sure if I just have the wrong config or because the bus network changed the way the DTC sees the CAN busses in the 2020 model.
Last thing, forscan is great for programming, services, etc., but it's horrible as a logger. It makes really inefficient requests and disconnects if somelike like TC is activated for some reason...
Message me and i'll send you a dbc file if you want to mess around with them. CSSelectronics has great info if you want to see the formatting and in depth info.