There is no reason to use MySQL, the homes are per map, and adding a mysql would be unnecessary bloat for this kind of plugin.
I get that but unless you remimber to phisicly go into the folder pertaining the database files and delete them when you wipe the server, they will still exsist on the freash wipe. Most people who use MySQL like myself spicificly wipes the data in the database itself when wiping the world folders. so its not so much bloat as it is a convinance option to have because you dont have to phisicly remimber to wipe the sqlight database files in the plugins folder and when you boot the server after a freash wipe by deleting the tables in the MySQL database and the world files, there is no left over information like it is now.
If I was to wipe one of my servers right now and I didnt know that the database files for the plugin itself was held in the plugin folder and I logged in after wiping the world files on a diffrant map, My homes are still there in the plugin folder so if I tried to set a home after a wipe it yells at me and say sorry this home already exsists so then you have to phisicly use the commands to remove the home and reset the home after a freash wipe. Allowing a user to have the MySQL option allows the user to have his own database used for it so when he wipes the world files he goes into his databse and deletes the tables as well which 100% gets rid of all databse information from the server.
So what you call bloat is a mater of convinace for those that are not aware that the plugin does a database NOR relize that those database files are in the plugin itself because they use there own MySQL database. I LITRALLY do a lot of copy and pasting and I copied my plugin folder from 1 location on my PC to 1 of my Ragnarok server NOT EVEN BEING AWARE that there was database files in one of the plugin folders and so I ended up coping OLD home databse information. So when I teliported using /home Home on my ragnarok server, insted of teliporting me to my base in vicking bay 3 it teleported me ALL THE WAY in the middle of the god dang ocean on the other side of the blue obilisc and /home Home should have put me in viking bay 3 not all the way freaking over there. If I had MySQL and has it attached to my own database, when I made a database for that server spicificly, I would have never had LEFT OVER FILES I didnt know about that was transfering that caused this problem. It was SUPER INCONVINANT that my home on my ragnarok server was in a diffrant spot on the blasted map because all I did was transfer my world files from a hosted site to self hosting and never even KNEW about the database files in the plugin folder. Litrally took me an HOUR to track down and figure out why my homes werent the same from the hosted site to self hosting were if I was using MySQL like I was for that hosted site and I transfered the database to my own MySQL like I did, I would have still had my homes SPICIFICLY for that server insted of trying to backtrack and figure out why the hell my homes no longer worked properly after making the switch from hosting to self hosing.
I apolojioze for the long winded discription of what happened to me personally but it was the best reason to describe why I was asking for it and what happened that made me ask for it.
Its a matter of convinace for those that use MySQL not bloat like you say because this issue could have been prevented and the information transfered over to my self hosting if it had a MySQL option when I transfered the database to my own self hosted databse from a hosted database.
100% could have been prevented if it was useing MySQL insted of making its own database files that I DIDN'T know about and took me an hour to figure why it was BORKED. Thats an HOUR of time wasted that didn't need to be wasted if the plugin had a MySQL option for those that use MySQL because the database would have been trasnfered from hosting to self hosting using mariaDB or whetever method of transfering databses or wiped when the MySQL user wiped the databse tables and world files leaving 0 leftover information that could have caused this issue and wasted time.
MySQL IS A CONVINIANCE to PREVENT issues NOT bloat for those that use it.