Thanks, I updated the Wiki page to reflect the new fee.
Incidentally, the size gets rounded up, so the number used for the calculation if there is even one byte over 35K means 36 is the needed value. Your fee was 0.0035 so the logic in the code would by default leave your transaction as low priority.
There is no way to modify the fee for an existing transaction. If it was sent using Blockchain.info, eventually it will stop retrying and the funds will again show as spendable.
Is suppose what could be attempted is to take one of the inputs and try to double spend it:
- https://blockchain.info/create-double-spend
Then that would invalidate this transaction, causing the funds to immediately become spendable once again.