It’s not. Your situation is literally a storage location being unavailable. Which is a solved issue under normal setups.
The forums and documentation is littered with the recommendation to use one HDD per node. That clearly covers storage spaces and you can’t really expect storj to address any for of exotic setup like with junctions. But yeah, you’re using junctions to also combine HDD’s so it’s covered by that as well.
There is also an official way to move db’s to SSD which you didn’t use.
I know it sucks, but your setup was a little janky and you’ve added more failure surfaces by adding more HDD’s that were critical for the working of your node. You can’t really blame Storj when running such a setup.
They haven’t. I feel a little like a broken record here, but the issue I addressed there has since been resolved. Your exotic setup broke that solution.
This is literally what the node now does.