In my very humble opinion (haven't had the extremely fortunate fortune to be formally educated on DAC and in general the math involved there), I think that discussion is greatly valuable. When you are compounding information into information you can never become accurate enough. Error accumulates - that is the woe if digital composition.
I would love to accelerate all this stuff on a GPU - given workable knowledge on how to specifically turn all those crazy mathematical formulas into code; which given only a rip-off degree is practically impossible.
When it comes to clipping or loss of data on the lower end, well, 32-bit floats have an 8 bit exponent (254 reasonable values); that means that the loudest full-precision unclipped signal is 765 dB (!) louder than the softest un-quantized signal. Even with mediocre centering, that's more than enough.
I don't think 64-bit audio is likely to be noticable, even for processing purposes, outside of really specialist kind of niches.
Most of it is convolution or multiply/accumulate, nothing crazy at all.
I learnt convolution in my own time, so if you have resources (that don't include integration) I would absolutely love to read them. DSP is something that seems hard and I'd love to get into it.
I keep track of a large number of resources for learning DSP over at http://diydsp.com
Take a look at the Theory, FAQs and Books sections. There are some recommended books, links to university course lectures, etc.
If you want to "render", i.e. produce a final .wav file from your input tracks, with applied effects, filters, gain-changes,... most DAW let you output a .wav-file with floating point data (not that it would make sense).
https://imgur.com/MJvf3cJ
But, you probably guessed it, there are people already discussing the merits of 64bit floating point over 32bit floating point (e.g. "double" over "float")... [already in 2007] https://www.gearslutz.com/board/music-computers/117203-does-...