Serviio on SSD - avoid writes

As the topic implies I am trying to eliminate unnecessary writes to the OS SSD disk on which Serviio is installed.

So far this has required the following modifications.

Serviio Console - Configured to transcode to writeable location.

File:
Serviio.Service.exe.vmoptions
Line:
-XX:-UsePerfData
Result:
Stops performance data being written to the %temp% directory.

File:
log4j.xml
Line:
<param name="File" value=D:/writeable/Serviio.log />
Result:
Serviio will debug spew into the file above.

File:
Derby.Properties
Lines:
derby.stream.error.file=D:/Serviio/derby.log
derby.storage.tempDirectory=D:/Serviio/Lib
Result:
Library Database log files and temporary files are written into the above locations.

However; as Clarkson would say "there is a problem. . ."

exe4j which Serviio employs to give the Java Run Time a meaningful instance name under windows - 'insists' on generating crap in %temp% and so far I am sufficiently unskilled or time poor to have discovered how to remedy this issue such that all non permanent writes are fielded away from temp.

Specifically:

exe4jlib.jar
i4del.exe

Are created in a folder with a random name similar to

e4j4BC7.tmp_dir1397300404

I want to stop this happening all together - and write some config somewhere to avoid this from happening - this is the only temporary write to my SSD of any process - so it would be nice to kill it off.

(I could put a junction in place for the %temp% folder - but I prefer to catch these process and configure them - as sometimes they get junction indigestion! )

Any skilled java folks able to help - much appreciated.

[Iveky]

why not change windows temp variable to something you like?

Sent from my LG-E440 using Tapatalk 2

Because of issues caused by an established OS - having tattooed the registry with a hard coded path.
That is to say - it is viable to modify a fresh installation with a 'better path' when that OS is 'new'
But years down the line (as I am) many badly behaved processes (programs) will evaluate the variable and 'assume' it will never not be available and hard code that into their configuration - either in the registry or in textual configuration files of some sort. So for this reason - if I had to do it - it would be via the junction option I refer to in my original post.

Thanks for the suggestion - but please can readers assume this is not answered and this question is outstanding for an answer still.
Thanks.