Just like data type checks (ex: regex whitelisting for field values) they need to be done at both the front end and backed and yes some times it's a pain but in the long run that's a positive not a negative. If you expose your database to a whole new app, say v2 of your app or an orthogonal admin interface, you can be assured of relational guarantees between your tables.
Yikes! You are missing the 'C' in ACID at the very least.
If what you say is true, a relational database might not be what you need to be using.
I think it is more likely that a relational database would be helpful to you but you worry about data after you worry about logic. A dangerous approach in many cases IMHO.
Keeping your "business logic" in the app as reasoning... You could just say that the business logic is built into the schema and shouldn't be there and just use a key store (many people do this, actually...); or you do all your transactions in the app. To my way of thinking, that's short-sighted.
As for slowing you down, FKs shouldn't, in terms of development (a good ORM handles it with ease), or in terms of physical performance (most databases handle performance constraints at this level via query optimisation and join strategies, at its worst you do bulk updates via a database facility).
FKs are a kind of business logic and I want none of that in my DB. I want my DB to give me storage, preferable ACID storage, and nothing more. I'll keep my business logic in my app.