Here's my feedback and ideas.
First a bit of coding advices in order to reduce the memory usage :
-as I explain earlier use setup for constant variables.
-don't duplicate an array when you don't need to create a new instance, simply use an index.
-many of your arrays used to create instances include static variables. So split the constant and the variables you need for new instances.
Let's take your classes arrays as an exemple, let's say "warrior".
They include variables that are constant and common to all raiders created, like "role" or "type" (of damage). And variables that are individual to each instance, like "cur_hp" or "lust".
So the first step is to reallocate the warrior (and other classes) class to setup. Second, split static and dynamic variables. You can keep "warrior" to store constant values and create a new classe "raider_inst" for creating raiders instances. Third when you create a new raider (or need to access a warrior attribute) only use an index instead of copying the all array.
Classes declarations
set setup.classes = {warrior:{role:"Melee", type:"Physical", ...}, priestess:{role:"Support", type:"Magical", ...}, etc.};
set setup.raider_inst = {class:"", cur_hp:0, lust:0, etc.};
New instance creation
set _newRaider = setup.raider_inst;
set _newRaider.class = "warrior";
Accessing values
setup.classes[_newRaider.class].role;
Now some gameplay ideas :
-I don't like having to wait 3 days before being able to interact with a newly enslaved raider. I suggest that instead of waiting, the player has to break the girl (obviously by having sex with her) to make her submit and become a slave. This stage could be developed in the future. For exemple I think it would be a good idea to reveal the traits of a captured raider only after you've broken her.
-The monsters HP stat and the healing spell need a rework. Atm it doesn't make much of a difference if your monster have 1 or 100 HP. That's why I suggest making the healing spell unable to revive monster.
-Globally, as the game is in an early stage and most things aren't unlockable, you should increase the capacity of the dungeon. The players can't do much with their slaves for now, so at least let them have more than 2. About that I don't like games that forces arbitrary limits on the player without any reason. I think a better design is to indirectly limit the player, by having his choices have concequences. A simple exemple is upkeep cost. I rather be forced to sell a slave because I can't keep up with the financial expenses than being told "sorry you only got 2 spots now". Of course in this situation an upkeep cost seems hard to implement, hard to imagine a slave costing too much to support. But an idea could be to make slaves rebel or escape when they're not attened for a few days.
