I think first you would have to enter the data manually, then come up with a way to generate a script that could be included in an upgrade.
Probably your script file would have to be utf-8 instead of ansi/ascii.
Then if you submit it to me I wll test it and as long as it doesn't cause errors running the script on dbs with latin collation then I can include it in an upgrade.
You can find the examples where we insert the exisiting data in the /Setup/applications/mojoportal-core/SchemaInsallScripts/mssql/18.104.22.168.config script.
But as I recall there were problems even with the existing data errors occured, for example the German city listed in the script as "Baden-Württemberg" lost special characters on import and the result is "Baden-W?rttemberg". So I fear the same thing would happen for all the Persian characters. Maybe/probably there is a solution but I have not had time to research it.